Let’s continue our discussion on the standard COBie format for BIM in facility maintenance management. Today, we will focus on how COBie addresses BIM requirements within the model. For COBie to function effectively as the primary information exchange standard, certain object attributes, spatial definitions, and project details must be included in the BIM model. The key specifications are:
- Unique asset names
- Asset identification by type
- Asset classification (e.g., OmniClass)
- Recognition of product and equipment locations within named spaces
- Relationships between spaces and zones
- Relationships between equipment and systems
- Warranty information
- Identification of jobs, resources, spare parts, and replacements
- References to contract documents
- Verification of external systems
- Identification of information sources
When exchanging COBie data using a simple electronic spreadsheet, the underlying data architecture follows these principles:
- All data types are contained within a single spreadsheet.
- The spreadsheet adheres to the default standard format.
- Color coding is applied to indicate different data types and their significance (see Table 1 and Figure 1).
- Lists within the spreadsheet link related information.
- References to external file archives are supported.
- The format is customizable to meet project-specific requirements.
The COBie standard not only uses color coding to highlight importance but also organizes various information categories into separate worksheets. As illustrated in Figure 2, the COBie spreadsheet connects the design, construction, and project delivery phases throughout the entire lifecycle. Table 2 provides further details about worksheet contents and their corresponding data source phases.
Beyond spreadsheet-based data exchange, COBie also supports data transfer via the IFC format, structured around the Information Delivery Manual (IDM). The IDM’s primary objective is to define the processes users follow throughout an engineering project’s lifecycle to exchange information efficiently. It clarifies the IFC data content required to support these processes, ensuring that IFC definitions, details, and descriptions remain clear and usable throughout the project.
The IDM’s technical architecture involves both BIM users and software vendors, adding layers of complexity to the information exchange. As depicted in the technical architecture diagram in Figure 3, the Process Map and Exchange Requirements primarily address BIM users, while the Functional Parts are relevant to software vendors.
A Process Map outlines the sequence of steps needed to complete a specific task—such as structural analysis, cost analysis, or estimation. It details the process configuration, the roles involved, the input information required, the data used, and the outputs generated, all within defined boundary conditions.
Currently, the COBie standard includes 10 main process diagrams covering various scenarios, including transmission review, equipment trial operation, and handover documentation.
Exchange Requirements specify the exact sets of information that must be exchanged to support business processes at specific project stages. At present, COBie defines 14 exchange requirements, including floor configuration, space configuration, asset categories, asset locations, and asset components.
Functional Parts describe individual software-created components that fulfill these exchange requirements. These components represent discrete information exchange actions linked to specific data within the exchange requirements. For example, when exchanging building models, components such as walls, doors, windows, floors, and roofs are essential.
Each functional component includes detailed technical specifications based on its exchange action. Since these actions may appear across multiple exchange requirements, functional components can be linked to several requirements and are designed for reuse.
That concludes today’s overview of the standard COBie format for BIM and facility maintenance management. Tomorrow, we will present a practical example to further illustrate these concepts.
Must log in before commenting!
Sign Up