The COBie data schema is structured as a relational database made up of 19 data tables.

Key Values
As with all databases, each data table must have a unique key for each row of data in the table (record). For most of the data tables, that unique key is the first data column, “Name”. For some tables, it is not expected that the value for the “Name” data field be unique, so the value in that data field alone cannot be used for the unique key. For those tables, the key is a combination of the values of several data fields in the record (compound key). The compound key is a concatenation of the values separated by an underscore and could be a concatenation of two or three fields. This means the format of the unique key will always be one of the following:

     Name

     Name_Field1

     Name_Field1_Field2

For example, The COBie.Attribute table requires a compound key of three fields:

     Format:  Name_Table_Table.Name

     Example:  Fan Max Speed_Type_Boiler Type 1

The following shows the key values for each data table:

Often, the “Name” key value in a COBie deliverable is equivalent to the designation of that asset in the equipment schedules in the contract document set used for the facility, structure, or group of structures. But, when aggregating the data from these equipment schedules into a COBie deliverable, duplicate values could arise. For example, the pump schedule may have a P-1 designation for a pump, but the plumbing fixture schedule may have a P-1 designation for a water closet. These values will have to be modified or augmented to be COBie compliant (by concatenating other data onto the name/key values, such as the type of asset).

Data Fields
Each data table contains several data fields, and these data fields are pre-defined as part of the COBie standard. The “Data Fields” section provides the details on each of the data fields.

Reference Fields
Data fields can be related to other data fields in the database that exist in the same data table or other data tables.

For example, the value for the “Manufacturer” data field that is on the “Type” data table is a reference to the “Name” data field that is on the “Company” data table. This way, a change to that “Name” on the “Company” data table will propagate across to all other data tables referencing it.

Status
Each data table and each data field include a status related to its requirement and there are eight available. When COBie is delivered in SpreadsheetML format (Microsoft Excel), each requirement has the option of also being color-coded for easy recognition.

1. Required
   Data tables and data fields that are always required with every COBie deliverable.
   SpreadsheetML Color: #FFFF99

2. Required (Reference to Another Data Field)
   Data fields that are required and whose value references a different data field, either in the same data table or a different data table (including the PickList data table). This status is not used for data tables, only data fields.
   SpreadsheetML Color: #FFCC99

3. Only If Specified in the Contract
   Data tables and data fields that are optional and only required if specified in the contract related to COBie deliverables.
   SpreadsheetML Color: #CCFFCC

4. Only If Specified in the Contract (Reference to Another Data Field)
   Data fields that are only required if specified in the contract and whose value references a different data field, either in the same data table or a different data table (including the PickList data table that has a status of "Only If Specified in the Contract"). This status is not used for data tables, only data fields.
   SpreadsheetML Color: #CCFFFF

5. External Reference
   Data fields whose values contain information that allows the data to be referenced back to the computer software that initially generated that information (Originating System). This status is not used for data tables, only data fields.
   SpreadsheetML Color: #CC99FF

6. Secondary Information When Preparing Product Data
   Data tables and data fields that are optional and only required if specified in the contract related to COBie deliverables, and that include secondary information not normally contained in a COBie deliverable.
   SpreadsheetML Color: #C0C0C0

7. Regional, Owner, or Product-specific Data
   Data tables and data fields that are required due to superseding regional, owner, or product-specific requirements.
   SpreadsheetML Color: #99CCFF

8. Not Used
   Data tables or data fields not used in the COBie deliverable.
   SpreadsheetML Color: #000000