6D / ASSET INFORMATION / SINGAPORE
Asset Information & COBie Handover
Prepare asset information that the receiving team can check and use. SBT’s 6D scope connects models, asset records, classifications and documents to agreed handover requirements.
DELIVERY BASIS
Defined information inputsDocumented review criteriaTraceable outputsView deliverables ↓SCOPE / DELIVERY
Turn dispersed project information into a controlled handover package. Agree the asset population, required fields, source responsibilities and receiving-system rules before extracting data; a model export alone does not establish a complete handover.
KEY OUTPUTS
- COBie / asset-information package
- Identifier and classification mapping
- Data dictionary and responsibility record
- QA and handover record
Project context
Turn dispersed project information into a controlled handover package. Agree the asset population, required fields, source responsibilities and receiving-system rules before extracting data; a model export alone does not establish a complete handover.
Inputs & requirements
- Asset Information Requirements (AIR) or agreed handover specification, asset scope and receiving platform.
- Required COBie version, exchange format, field definitions, units and acceptance tests.
- Models, equipment schedules, supplier information and relevant O&M or commissioning documents.
- Project tag rules, selected classification tables and editions, permitted use and named data owners.
Share a non-confidential requirements summary first. Restricted project information should only be exchanged through an agreed secure route.
Technical method
- Define required fields and responsibility for supplying, checking and accepting each information group.
- Prepare the asset register and agreed COBie dataset; link assets to model objects, systems, locations and supporting documents.
- Apply project-required identifiers and classification fields using the agreed sources and versions. Keep unresolved values marked for action.
- Validate the package, reconcile exceptions and conduct a receiving-system import or sample acceptance check within the agreed scope.
Deliverables
| Output | Purpose |
|---|---|
| COBie / asset-information package | The agreed data structure and format, with the applicable version recorded. |
| Identifier and classification mapping | Traceable relationships between asset IDs, project tags, model objects and selected classification fields. |
| Data dictionary and responsibility record | Field meaning, source, owner and required delivery stage. |
| QA and handover record | Completed checks, exceptions, supporting references and receiving-party acceptance status. |
Review criteria
- Required fields, formats, units and duplicate or missing identifiers.
- Relationships between assets, types, systems, locations, model objects and documents.
- Classification table / edition and identifier provenance; links open for the intended receiving role.
- Model-to-register reconciliation and receiving-system sample tests. Format validation does not prove that supplied equipment data is factually correct.
Information & application
Four terms, different purposes
- COBie
- A structured exchange of non-geometric asset information for handover. It is not a procurement BOM or simply an export button. buildingSMART background
- KKS
- A plant identification system used particularly for energy facilities. Apply it where the project requires it, using the relevant rules and licensing arrangements. vgbe guidance
- Uniclass
- A classification system with tables for different kinds of built-environment information. Select the appropriate table and edition for the object being classified. NBS Uniclass
- OmniClass
- A construction-information classification system with separate tables for different information facets. Use the project-specified table and edition. CSI explanation
A classification describes a category, not the unique identity of an installed asset. Store asset IDs, project tags, model object IDs and classification fields distinctly. Do not assume a one-to-one conversion between classification systems. Confirm applicable versions and usage permissions; this service does not distribute complete standards tables.
These information requirements can begin during design and develop through procurement and construction. They should not be left until the final export.
Responsibilities
SBT prepares and checks information against an agreed requirement. Suppliers and appointed parties remain responsible for their source data; the receiving party confirms acceptance. Our 6D label describes this service scope, not a universal industry definition.
Common questions
Is COBie the same as a procurement BOM?
No. A procurement BOM supports purchasing and is addressed in our 5D quantity service. COBie is an asset-information exchange for handover and operational use.
Must a project use KKS, Uniclass and OmniClass together?
No. Apply the identifiers and classifications required by the client and receiving system. The choice, table, edition and permissions should be agreed before preparation.
Can a classification code replace an asset ID?
No. Multiple assets may share a classification. A reliable asset identity and its links to project tags and model objects are still needed.
Does having a BIM model guarantee a complete handover?
No. Manufacturer data, documents and accepted asset records may come from several parties. Missing information must be resolved with its owner, not guessed.
PROJECT ENQUIRIES
Discuss Your Project
Tell us your project stage, disciplines and BIM support requirements.
Singapore-based, supporting projects locally and internationally.
Monday–Saturday · 08:00–18:00 SGT Sunday closed