COBie is successful when all project stakeholders are involved. These include the architects, engineers, contractors, suppliers, tradespeople, commissioning agents, and the facility owner. Each has a role in providing – in the COBie standardized digital format – information related to the maintainable assets of that facility during the project. This data is delivered at specified milestones in the project, culminating in a full delivery at project handover.

COBie has typically been used for building design and construction projects but can also be used for infrastructure projects or to transfer facility ownership from one party to another. Throughout this document, facility is used to include both building and infrastructure assets.

The COBie format is a subset of the contents of a Building Information Model (BIM). It is non-graphic data defined as a Model View Definition (MVD) of the Industry Foundation Class (IFC) schema. It can also be represented in a spreadsheet format.

The structure of the tables that make up COBie includes hierarchies based on the data types:

Each data table includes a standardized set of data fields, and each field is designated as either always required, required if stated in the contract, or a reference to another field in the database. The COBie standard allows asset owners to define the specific fields they want in their data delivery. In fact, it provides the best results for asset owners when they specify what they require to be delivered.

V3 of the COBie standard incorporates 58 different updates grouped into four categories.

This document is copyright-protected by the National Institute of Building Sciences (NIBS). While the reproduction of working drafts or committee drafts in any form for use by participants in the NBIMS-US™ standards development process is permitted without prior permission from NIBS, neither this document nor any extract from it may be reproduced, stored, or transmitted in any form for any other purpose without prior written permission from NIBS. For more information, visit the NIBS website at https://www.nibs.org/.

Industry Foundation Classes (IFC) and the FM Handover Model View Definition (MVD) are both open standards protected under a “creative commons” license as buildingSMART International (bSI) intellectual property. For more information, please see the bSI website at https://www.buildingsmart.org/.

The Construction to Operations Building information exchange (COBie) specification provides a standard organization of data used to manage and maintain facility assets. It is a combined set of all space, product, and equipment schedules found on associated design drawings as well as a compilation of as-built, operations & maintenance (O&M), and commissioning information captured during construction.

The COBie specification provides a standardized method for project teams to deliver the data necessary to maintain a facility in a digital format. This allows the facility owner the ability to populate their facility maintenance system quickly and accurately with the data needed. COBie can be used whenever a handover occurs, including:

• At the end of new construction
• At the end of a renovation
• When an existing facility changes ownership or management

COBie is not limited to buildings. It can be used to quickly deliver data related to maintainable assets on infrastructure projects that may not include buildings. Though not optimized for infrastructure projects, COBie can certainly be adapted to work on those types of projects, especially small to medium-sized ones.

The COBie specification was initially published for NBIMS-US™ V2 (National BIM Standard-United States®) and was defined as a Model View Definition (MVD) of IFC (Industry Foundation Classes). The release of NBIMS-US V3 in 2015 included the most current version of the COBie specification, V2.4. Since that time, the COBie Work Group at NIBS has been working on updating COBie to better align with the evolution of BIM in the US. This work has culminated in a new V3 to be released in 2023 and as part of NBIMS-US V4.

This document details the latest version of COBie, Version 3. It includes information related to:

• The process of using COBie, overall and for different project types
• The structure of the COBie specification
• The definitions of the schemas related to COBie (Appendix)
• A log of the changes from the previous version 2.4 (Appendix)

Copyright
This document is copyright-protected by the National Institute of Building Sciences (NIBS). While the reproduction of working drafts or committee drafts in any form for use by participants in the NBIMS-US™ standards development process is permitted without prior permission from NIBS, neither this document nor any extract from it may be reproduced, stored, or transmitted in any form for any other purpose without prior written permission from NIBS.

buildingSMART International (bSI)
Industry Foundation Classes (IFC) and the FM Handover Model View Definition (MVD) are both open standards protected under a “creative commons” license as bSI intellectual property. For more information, please see the bSI website:
https://www.buildingsmart.org/

OMNICLASS ®
The trademark OMNICLASS(R) and the copyrighted OmniClass work are used under license from the Construction Specification Institute, Inc.

The following terms are used throughout this document. Footnotes refer to links with additional information in the Appendix A: Resources section.

This section outlines the recommended process for generating and submitting a COBie standard deliverable during a project.

The general process for generating a COBie deliverable is to specify what data is wanted, when it is wanted, and who will deliver and review it. A COBie deliverable may be generated for any phase of a construction project, but the specific tables and fields must be selected or specified to populate or update (see Structure section). Each table has required fields that may be prerequisites to using other tables. Most projects find success using COBie when it is addressed at the beginning of the project.

One COBie file shall be provided for each facility. If there are multiple facilities, then an additional COBie file identifying the assets for the site shall also be provided.

In design and construction projects, the ultimate purpose of COBie is to deliver information about assets in a facility to the next owner/manager at the end of a phase in the project lifecycle. Typically, this is the owner at the end of construction, but it can also be applied to intermediate handovers between consultants during the design and construction process. These handovers may not include all the information ultimately required, but they can still provide valuable pieces of that information to assist other consultants (for example, from the design architect to the construction contractor at the end of design). Interim deliverables are sometimes called “data drops” and are also valuable to allow the project team to build up the process and information ultimately needed by the end of the phase to help ensure that the final handover is successful and includes the content required. Even though interim requirements are not required for all projects utilizing COBie, they are strongly recommended, especially for larger projects. Common milestones where it would be beneficial to include a data drop are end of conceptual design, end of design development, end of construction documentation, and at fixed intervals during the “in-use” phase of a facility. 

The minimum requirement for a COBie deliverable is to populate the required fields in the required tables. Any additional tables and fields must be specified that are required by the person or company who will provide the COBie deliverable. Also specify who will manage and transfer COBie deliverables at each phase to ensure proper coordination between phases. What tables and fields to select depends on the desired use of the COBie deliverable for each phase, but it is recommended to start with the end in mind.

COBie has required field statuses for most tables and some fields are prerequisite to using subsequent tables. The reference and if-specified field statuses are prescriptive once the required fields are completed for each table. A list of required, reference, and if-specified field statuses are in the Structure section. When selecting tables and fields to use for a project, specify how much information is necessary for each type of equipment, because it may not be useful to collect COBie data for all equipment in the built environment. For example, it may not be useful to spend the effort collecting the serial number for every light fixture if the policy is to replace it with a similar type when it is unrepairable. However, it may be necessary to collect the serial number for equipment with long warranty durations to assist with filing a possible future claim.

The scope of a construction project can be small, such as changing a filter in a building, or enormous, such as constructing a twelve-mile-long subway. Construction projects are temporary endeavors that take place over time and are composed of phases. The Construction Specification Institute (CSI) recommends nine (9) phases and defines them in OmniClass Table 31 (dated 30th October 2012 and found at http://www.omniclass.org/). CSI lists the phases in order of a traditional construction project life cycle; however, work activities may occur in more than one phase simultaneously. For example, the Design Phase may be revisited to modify construction drawings due to unforeseen conditions while the remaining work continues in the Implementation Phase. In this example, an update may be required from the people responsible for the Design Phase and the people responsible for the Implementation Phase.

The table below indicates which COBie tables will likely be updated at each phase of construction and the following is a guide to help select which fields to update at each phase.

The BIM Execution Plan for the project should specify which phases a COBie deliverable is wanted, and who will be responsible for updating each field within the deliverable. The National BIM Standard-United States® (NBIMS-US™) includes a section on BIM Execution Planning. For some larger, more complex projects, a COBie Execution Plan may be needed to define all the owner requirements for COBie deliverables, including the roles and responsibilities for data management.

Sub-phases/milestones may also be specified such as “Construction Documents - 2” or a number of days prior to substantial completion. For example, specifying that the designer is responsible for updating the name, type, and location of equipment during the Design Phase at CD-2, while the constructor is responsible for updating the manufacturer, model number, and serial number information during the Implementation Phase at 120 days prior to substantial completion. In this scenario, the constructor will use the COBie data created by the designer to develop the deliverable for the Implementation Phase. Therefore, also specify the transfer of responsibility of the COBie data from one person to another for each phase of the construction life cycle (primarily, what fields the person must keep up to date during the duration of their responsibility). Transfers of responsibility could be designer-to-owner, designer-to-constructor, owner-to-constructor, constructor-to-operator, operator-to-operator, owner-to-owner, owner-to-designer, etc. The transfers will vary depending on the category of projects such as new construction, renovations, operations and maintenance, or demolition. For example, a new construction project may generate COBie data for the first time, so the first transfer may be designer-to-constructor. For renovation projects, the owner may provide existing COBie data to the designer, which is owner-to-designer.

A BIM Execution Plan, or COBie Execution Plan, should designate who will review content in each COBie deliverable. For example, the facility manager could review fields related to equipment and ensure that they have sufficient data for operations and maintenance. The space manager could review space data and ensure it has the correct names, categories, zoning, etc. It is recommended to place more emphasis on reviewing the initial deliverables to clarify and express your expectations for the next deliverables.

Consider using tools to automate submittal reviews. These tools can be very useful in validating the proper formatting in a COBie deliverable and provide feedback to the authors. Several tools are freely available to check the structure of the COBie file or even to validate COBie data in BIM models before generating a COBie deliverable (either for structure or against project requirements).

This section details the structure for the COBie standard.

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

The data tables in COBie each serve a purpose and are organized in a hierarchy related to a facility, structure, or group of structures.

In the following descriptions, the primary Key Value (data field) for each data table is shown in bold, where applicable. This Key is always the “Name” data field and does not exist for the Instruction and PickList data tables.

Table 1: Instruction

Table 2: Company

Table 3: Facility

Table 4: Level

Table 5: SpaceType

Table 6: Space

Table 7: Zone

Table 8: Type

Table 9: Component

Table 10: System

Table 11: Resource

Table 12: Job

Table 13: Event

Table 14: Package

Table 15: Risk

Table 16: Document

Table 17: Attribute

Table 18: Coordinates

Table 19: PickList

Each data table contains several data fields, and these data fields are pre-defined as part of the COBie standard.

Naming
Data field names utilize the following naming conventions:

1. Names do not contain any spaces.
2. The first letter is always capitalized, and all subsequent letters are lower case.
3. If more than one word is used for the data field name, then the words are placed together without a space in between and the first letter of each word capitalized (for example, “PartOf" or “EndDate”).
4. When a data field references a different data field, either on the same data table or a different one, then the name is a combination of the data table name and the data field on that data table, separated by a period (for example, the "Component.Name" data field on the “System” data table). This is how all the data fields on the “PickList” data table are formatted, identifying the specific data fields and the data table on which they reside.

Organization
To better organize data fields on data tables, they are grouped together based on their purpose. There are six groupings:

• Identification – data fields used to help identify an asset.
• Classification – data fields used to better classify an asset.
• Location – data fields related to an asset’s location.
• External – data fields populated automatically by external software.
• Required – additional data fields that are always required for each COBie deliverable.
• Optional – additional data fields that are only required if specified in the contract.

The data fields on each data table are then sorted based on these groupings (in the order shown above). When more than one data field exists in a data table with the same grouping, then the data fields are sorted alphabetically. The only exception is the “Name” data field, as that is always the first data field on the data table.

Nomenclature
Throughout this standard there are references to specific data fields on specific data tables. To make it easier to identify these, the following nomenclature is used: DataTable.DataField. Often, this nomenclature will be preceded with “COBie.” For example, the “Name” data field on the “Type” data table would be represented as:

     COBie.Type.Name

Default Value
Data fields should not be left blank for a COBie deliverable. Instead, a value of “n/a” should be used (without the quotes) for text fields and “0” for real number fields.

Pre-Determined Values
Some data fields in COBie must be populated with values that are already determined. In other words, users must choose a value from a list and not type in their own value (or even an abbreviation of one of the pre-determined list of values). These lists of pre-determined values are known as PickLists and there is a data table in COBie to store them.

Some of these PickLists are constant for all COBie deliverables (such as COBie.Level.Category and COBie.Type.AssetType), while others will vary based on regional or owner preferences (such as using OmniClass Table 34 values for the COBie.Company.Category data field in the U.S. versus Uniclass Table Ro values for the same data field in the U.K.).

Custom Data Fields
It is not permitted to create custom data fields on data tables. Instead, utilize the COBie.Attributes data table to add additional data fields to your COBie deliverables.

The reason is because, as a standard schema, asset management systems can have pre-built data field mappings to allow for the import of data from a standard COBie deliverable without customization. If data fields are added to data tables, then asset management systems will not be able to recognize and import those data fields without first customizing the import tool.

Comma Separated Values
Some fields require a comma separated list of values. These include:

• COBie.Zone.Space.Name
• COBie.Component.Space.SecondaryName
• COBie.System.Component.Name
• COBie.Job.Priors
• COBie.Job.Resource.Name

Data Types
Each data field can be of a certain type of data. Included in the following pages is an indicator on the type of data for that data field, using the following legend:

• T     Text as a string of characters that can include letters, numbers, and punctuation. Unless otherwise noted:
  • The total field length should be limited to 255 characters or less.
  • Use only ASCII characters (0-9, A-Z, a-z, space “ “, dash “-“, and underscore “_”).
  • Should not include non-printing characters.
  • Name fields should not include spaces due to inconsistency of parsing software.
• R     Real Number
• D     Date (following the ISO 8601 standard)
• U     URL (Uniform Resource Locator or web address)

Details
The following pages details each of the data fields that are part of the COBie standard. This information includes the name, description, examples, and details regarding the organization and status.

INSTRUCTION

COMPANY

FACILITY

LEVEL

SPACETYPE

SPACE

ZONE

TYPE

COMPONENT

SYSTEM

RESOURCES

JOB

EVENT

PACKAGE

RISK

DOCUMENT

ATTRIBUTE

COORDINATE

PICKLIST

There are several approved formats in which the COBie database can be delivered. These include:

For details on these formats and their corresponding schema, see the “Appendix” in this document.

The following resources are referenced in this document.

ISO/IEC 10303-21:2016

There are three related parts to the ISO standard related to the STEP Physical File (SPF) format:

• ISO 10303-11, Industrial automation systems and integration — Product data representation and exchange — Part 11: description methods: The EXPRESS Language Reference Manual. This is the format of figures found in the referenced MVD.
• ISO 10303-21, Industrial automation systems and integration — Product data representation and exchange — Part 21: Implementation methods: Clear text encoding of the exchange structure. This is typically referred to as the STEP Physical File Format.
• ISO 10303-28, Industrial automation systems and integration — Product data representation and exchange — Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas. This is typically referred to as ifcXML.

IFC Tables A, B, and C are intended to direct the reader to the most relevant pages of the IFC4.3 documentation:

http://ifc43-docs.standards.buildingsmart.org/

The COBie3 MVD and IDS contain the formal definitions.

IFC Table A – Mapping Between COBie V3 Tables and IFC entities
* Indicates an abstract entity where only its subtypes are used

IFC Table B – Mapping Between COBie V3 Fields and IFC Properties, Attributes, and Relationships
Relationships are listed right-justified.

IFC Table C – Expected IFC Subtypes for COBie V3 Type and Component Tables
It is up to the owner to put in the contract the list of maintainable assets. Typically, the following list is used. Refer to table 8 Type and Table 9 Component.

SPREADSHEETML FORMAT
ISO/IEC 29500-1:2016

SpreadsheetML is an XML schema reflecting the organization of spreadsheet data in Microsoft Excel. The use of SpreadsheetML format for COBie data is optional in this specification. The SpreadsheetML format represents COBie data in an easy to understand and digest format (human readable).

More information on the SpreadsheetML schema can be found here:

https://learn.microsoft.com/en-us/office/open-xml/structure-of-a-spreadsheetml-document

An example blank spreadsheet is included as part of this standard.

ISO/IEC 21778:2017
The ability to deliver COBie data in a JSON format is new for this version.

General

• There is a restriction that additional properties (user added columns) must be of type ‘string’.
• References within a JSON document should use JSON pointers. That means that the value of all references will have different values when delivered in JSON than when delivered in other formats.
• For references to the COBie.PickList table, there are specified enums for lists that are enumerated in the table. There are no references to external standards.
• This schema will be much easier for JavaScript applications to consume if the field names are valid JavaScript identities. Therefore, the COBie.X.Name field is replaced with ‘_Ref’ and it has been added to all table references.
• The COBie.X.Table and COBie.X.Table.Name fields have been replaced with a single ‘Table_Ref’ field that is either a JSON-pointer or an array of JSON pointers.

Instructions Table

• Version and Release should be numeric.
• All the unit fields are required, and the Organization column is updated to reflect that.

Facility Table

• COBie.Facility.Latitude, COBie.Facility.Longitude, and COBie.Facility.Elevation should be numeric as this assumes a +/- real number as used by GPS.
• Minimum and maximum constraints have been added to COBie.Facility.Latitude and COBie.Facility.Longitude.

Component Table

• COBie.Space.SecondaryName is rendered as ‘SecondarySpace_Ref’.

Job Table

• COBie.Job.Table and COBie.Job.Table.Name are rendered as arrays.
• COBie.Job.ResourceNames is replaced with ‘Resource_Ref’, which is an array of JSON pointers.

Risk

• The following fields have been replaced and each of them is single valued:
• COBie.Risk.SpatialTable and COBie.Risk.SpatialTable.Name with ‘Spatial_Ref’.
• COBie.Risk.PhysicalTable and COBie.Risk.PhysicalTable.Name with ‘Physical_Ref’.
• COBie.Risk.ProcessTable and COBie.Risk.ProcessTable.Name with ‘Process_Ref’.

Sample Schema

{
 "title": "COBie v3 JSON Schema",
 "$schema": "http://json-schema.org/draft-04/schema#",
 "$id": "https://www.nibs.com/Schema/COBie/v3",
 "description": "",
 "type": "object",
 "required": [
  "Instructions",
  "Company",
  "Facility",
  "Level",
  "SpaceType",
  "Space",
  "Type",
  "Component"
  ],
 "properties": {
  "Instructions": {
   "type": "object",
   "description": "Provides written instructions related to the COBie database, but also contains the general submittal information for a particular COBie deliverable.",
   "required": [
    "Title",
    "Version",
    "Release",
    "Status",
    "Region",
    "ExportDateTime",
    "AreaUnit",
    "CurrencyUnit",
    "DurationUnit",
    "LinearUnit",
    "VolumeUnit",
    "WeightUnit",
    "AreaMeasurementStandard",
    "CoordinateSystemDescription",
    "CoordinateSystemOrigin",
    "ClassificationSystem.Company",
    "ClassificationSystem.Facility",
    "ClassificationSystem.SpaceType",
    "ClassificationSystem.Type",
    "ClassificationSystem.System"
    ],
   "properties": {
    "Title": {
     "type": "string"
    },
    "Version": {
     "type": "number",
     "default": 3
    },
    "Release": {
     "type": "number",
     "default": 0
    },
    "Status": {
     "type": "string",
     "description": "The version IFC with which this COBie deliverable aligns.",
     "default": "IFC4"
    },
    "Region": {
     "type": "string",
     "description": "Format is ISO-639-1 two letter language code",
     "examples": [
      "en-US",
      "en-GB"
     ]
    },
    "ExportDateTime": {
     "type": "string",
     "format": "date-time",
     "description": "Format is ISO-8601 (YYYY-MM-DD) with exact time optional",
     "examples": [
      "2022-12-31",
      "2022-12-31T13:00:00"
     ]
    },
    "Milestone": {
     "type": "string",
     "description": "A description of the project milestone for which this COBie deliverable represents.",
     "examples": [
      "50% DD",
      "90% CD",
      "Handover"
     ]
    },
    "OriginatingCompany": {
     "type": "string",
     "format": "json-pointer",
     "description": "The name of the company that generated this COBie deliverable, referencing a COBie.Company.Name value.",
     "examples": [
      "/Company/3"
      ]
     },
     "AreaUnit": {
      "type": "string",
      "description": "From the 'Units.Area' field on the PickLists table",
      "enum": [
       "Square Inches",
       "Square Feet",
       "Square Miles",
       "Square Millimeters",
       "Square Meters",
       "Square Kilometers"
       ],
       "examples": [
        "Square Feet",
        "Square Meters"
        ]
       },
       "CurrencyUnit": {
        "type": "string",
        "description": "From the 'Units.Currency' field on the PickLists table",
        "examples": [
         "Dollars",
         "Euros"
         ]
        },
        "DurationUnit": {
         "type": "string",
         "description": "From the 'Units.Duration' field on the PickLists table",
         "enum": [
          "As required",
          "Day",
          "Minute",
          "Month",
          "Quarter",
          "Week",
          "Year"
          ],
          "examples": [
           "Month",
           "Year"
          ]
         },
         "LinearUnit": {
          "type": "string",
          "description": "From the 'Units.Linear' field on the PickLists table",
          "enum": [
           "Inches",
           "Feet",
           "Miles",
           "Millimeters",
           "Meters",
           "Kilometers"
          ],
          "examples": [
           "Feet",
           "Meters"
          ]
         },
         "VolumeUnit": {
          "type": "string",
          "description": "From the 'Units.Volume' field on the PickLists table",
          "enum": [
           "Cubic Feet",
           "Cubic Meters"
          ],
          "examples": [
           "Cubic Feet",
           "Cubic Meters"
          ]
         },
         "WeightUnit": {
          "type": "string",
          "description": "From the 'Units.Weight' field on the PickLists table",
          "enum": [
           "Ounces",
           "Pounds",
           "Tons",
           "Grams",
           "Kilograms",
           "Metric Tons"
          ],
          "examples": [
           "Pounds",
           "Kilograms"
          ]
         },
         "AreaMeasurementStandard": {
          "type": "string",
          "examples": [
           "BOMA 2017 for Office Buildings",
           "Standard Methods of Measurement (ANSI/BOMA Z65.1—2017)"
          ]
         },
         "CoordinateSystemDescription": {
          "type": "string",
          "examples": [
           "Degrees, Minutes, Seconds"
          ]
         },
         "CoordinateSystemOrigin": {
          "type": "string",
          "examples": [
           "38°54'12.438\"N, 77°2'1.0314\"W"
          ]
         },
         "ClassificationSystem_Company": {
          "type": "string",
          "description": "Provide system name and version",
          "examples": [
           "OmniClass Table 34",
           "Uniclass Table Ro"
          ]
         },
         "ClassificationSystem_Facility": {
          "type": "string",
          "description": "Provide system name and version",
          "examples": [
           "OmniClass Table 11",
           "Uniclass Table En"
          ]
         },
         "ClassificationSystem_SpaceType": {
          "type": "string",
          "description": "Provide system name and version",
          "examples": [
           "OmniClass Table 13",
           "Uniclass Table SL"
          ]
         },
         "ClassificationSystem_Type": {
          "type": "string",
          "description": "Provide system name and version",
          "examples": [
           "OmniClass Table 23",
           "Uniclass Table Pr"
          ]
         },
         "ClassificationSystem_System": {
          "type": "string",
          "description": "Provide system name and version",
          "examples": [
           "OmniClass Table 21",
           "Uniclass Table EF"
          ]
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       },
       "Company": {
        "type": "array",
        "uniqueItems": true,
        "description": "Represents the information related to a company that is referenced elsewhere in a COBie deliverable.",
        "items": [
         {
          "type": "object",
          "required": [
           "Name",
           "Phone"
          ],
          "properties": {
           "Name": {
           "type": "string",
           "description": "The name of the Company. This is the primary key for this data table and each must be unique.",
           "examples": [
            "ABC_Corp",
            "xyzconstruction-com"
           ]
          },
          "Phone": {
           "type": "string",
           "description": "The telephone number for the Company.",
           "examples": [
            "+1 (202) 289-7800"
           ]
          },
          "Category": {
           "type": "string",
           "description": "The classification for the Company. This data field value comes from one of the values in COBie.PickList.Company.Category data field.",
           "examples": [
            "34-10 11 Owner",
            "Ro_10_20_14 Client"
           ]
          },
          "Website": {
           "type": "string",
           "description": "The website address for the Company.",
           "examples": [
            "www.abccorp.com"
           ]
          },
          "Street": {
           "type": "string",
           "description": "The street address for the Company.",
           "examples": [
            "1090 Vermont Avenue NW, Suite 700"
           ]
          },
          "PostalBox": {
           "type": "string",
           "description": "The postal box address for the Company.",
           "examples": [
            "P.O. Box 1234"
           ]
          },
          "Town": {
           "type": "string",
           "description": "The city or town address for the Company",
           "examples": [
            "Washington"
           ]
          },
          "StateRegion": {
           "type": "string",
           "description": "The state or regional address for the Company.",
           "examples": [
            "DC",
            "NC"
           ]
          },
          "PostalCode": {
           "type": "string",
           "description": "The zip, or postal code, address for the Company.",
           "examples": [
            "20005"
           ]
          },
          "Country": {
           "type": "string",
           "description": "The country where the Company is located.",
           "examples": [
            "U.S.A.",
            "U.K.",
            "Germany"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "Certifications": {
           "type": "string"
          },
          "Department": {
           "type": "string",
           "description": "The name of the department for the Company.",
           "examples": []
          },
          "OrganizationCode": {
           "type": "string",
           "description": "The organizational code for the Company."
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Facility": {
       "type": "object",
       "description": "Provides information related to the facility, structure, or group of structures (in the case of infrastructure projects) for which the COBie deliverable represents.",
       "required": [
        "Name",
        "Address",
        "Latitude",
        "Longitude",
        "Elevation"
       ],
       "properties": {
        "Name": {
         "type": "string",
         "description": "The name of the Facility for this COBie deliverable. This is the primary key for this data table and each must be unique."
        },
        "Descriptions": {
         "type": "string",
         "description": "A general text description of the facility, structure, or group of structures as part of this COBie deliverable."
        },
        "Types": {
         "type": "string",
         "enum": [
          "Facility",
          "Project",
          "Site"
         ],
         "description": "The type of facility, structure, or group of structures as part of this COBie deliverable. This data field value comes from one of the values in COBie.PickList.Facility.Type data field.",
         "examples": [
          "Facility",
          "Project",
          "Site"
         ]
        },
        "Category": {
         "type": "string",
         "description": "The classification for the Facility. This data field value comes from one of the values in COBie.PickList.Facility.Category data field.",
         "examples": [
          "11-27 25 19 Office-Retail Building",
          "En_20_15_10 Multiple occupation office buildings"
         ]
        },
        "Address": {
         "type": "string",
         "description": "The city or town address of the project in Facility.",
         "examples": [
          "1090 Vermont Avenue NW, Suite 700, Washington, DC 20005"
         ]
        },
        "Latitude": {
         "type": "number",
         "minimum": -90,
         "maximum": 90,
         "description": "The specific latitude for the facility, structure, or group of structures as part of this COBie deliverable.",
         "examples": [
          42.3584
         ]
        },
        "Longitude": {
         "type": "number",
         "minimum": -180,
         "maximum": 180,
         "description": "The specific longitude for the facility, structure, or group of structures as part of this COBie deliverable.",
         "examples": [
          -71.0598
         ]
        },
        "Elevation": {
         "type": "number",
         "description": "The specific elevation above sea level for the facility, structure, or group of structures as part of this COBie deliverable.",
         "examples": [
          354,
          14,
          115,
          5
         ]
        },
        "ExtIdentifier": {
         "type": "string",
         "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
         "examples": [
          "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
         ]
        },
        "ExtObject": {
         "type": "string",
         "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
         "examples": [
          "IfcSpace"
         ]
        },
        "ExtSystem": {
         "type": "string",
         "description": "The name of the computer system generating the row of COBie data.",
         "examples": [
          "Autodesk Revit 2023, Build: 20220429_1500(x64)",
          "ArchiCAD 19 Full (USA) / Build: 5005",
          "IBM Maximo"
         ]
        },
        "Description": {
         "type": "string"
        }
       },
       “additionalProperties”: {
        "type": "string"
       }
      },
      "Level": {
       "type": "array",
       "uniqueItems": true,
       "minItems": 1,
       "description": "Contains information related to the vertical levels of a facility or, in the case of infrastructure projects, the geographic areas such as the site surrounding a facility/structure, a rail or highway corridor, etc.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the Level.",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Level.",
           "examples": [
            "3rd floor area plan"
           ]
          },
          "Category": {
           "type": "string",
           "enum": [
            "Roof",
            "Floor",
            "Site"
           ],
           "description": "The classification for the Level. This data field value comes from one of the values in COBie.PickList.Level.Category data field.",
           "examples": [
            "Roof",
            "Floor",
            "Site"
           ]
          },
          "PartOf": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to another Level item on this data table to represent that this item is a subset of that one. For example, a facility on a sloped grade that has a single “Level 1” floor per the signage, but that is separated within by a few steps, so the model has two different levels defined to manage the elements.",
           "examples": [
            "Floor/23"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "Elevation": {
           "type": "number",
           "description": "The elevation at the top of the level structure. If allowable values are not specified by contract, the default value is measured as a relative value compared to the facility’s datum.",
           "examples": [
            354,
            14,
            115,
            5
           ]
          },
          "Height": {
           "type": "number",
           "description": "The distance between the top of level structure to bottom of structure above.",
           "examples": [
            10,
            12
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "SpaceType": {
       "type": "array",
       "description": "Provides information related to the different types of spaces that make up a facility, structure, or group of structures for this COBie deliverable.",
       "uniqueItems": true,
       "items": [
        {
         "type": "object",
         "required": [
          "Name"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Space Type.",
           "examples": [
            "Shared Open cubicles"
           ]
          },
          "Category": {
           "type": "string",
           "description": "The classification for the Space Type. This data field value comes from one of the values in COBie.PickList.SpaceType.Category data field.",
           "examples": [
            "13-55 11 Office Spaces",
            "SL_20_15_27 Enclosed offices"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Space": {
       "type": "array",
       "uniqueItems": true,
       "minItems": 1,
       "description": "Spaces represent the horizontal decomposition of Levels in COBie and which have common functional purpose and user.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Description",
          "Level_Ref"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "description": "The name of the Space. This is the primary key for this data table and each value must be unique and must not contain a comma. This is often the room number in the construction documents."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Space.",
           "examples": [
            "Bob's Office",
            "Conference room seating 12"
           ]
          },
          "SpaceType_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to an item from the space type data table."
          },
          "Level_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to an item from the Level data table."
          },
          "PartOf": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to another Level item on this data table to represent that this item is a subset of that one. For example, a large open Room that has cubicles within. Each cubicle space would be part of the large open space.",
           "examples": [
            "Space/105"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "GrossArea": {
           "type": "number",
           "description": "The total space area as specified in the design contract and calculated by the identified COBie.Instruction.AreaMeasurementStandard value.",
           "examples": [
            "1125.25",
            "3201"
           ]
          },
          "NetArea": {
           "type": "number",
           "description": "The usable space area as specified in the design contract and calculated by the identified COBie.Instruction.AreaMeasurementStandard value.",
           "examples": [
            "988.62",
            "3110.3"
           ]
          },
          "UsableHeight": {
           "type": "number",
           "description": "Distance from top of finished level to bottom of ceiling. If there is no ceiling, then this value must match COBie.Level.Height.",
           "examples": [
            "22",
            "120"
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Zone": {
       "type": "array",
       "description": "Zones represent the aggregation of Spaces that provide some common purpose.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Space_Ref"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the Zone.",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Zone.",
           "examples": [
            "Seating for the development orginization"
           ]
          },
          "Category": {
           "type": "string",
           "description": "The classification for the Zone. This data field value comes from one of the values in COBie.PickList.Zone.Category data field.",
           "examples": [
            "Circulation Zone",
            "Occupancy Zone"
           ]
          },
          "Space_Ref": {
           "type": "array",
           "minItems": 1,
           "description": "An array of json-pointer references to an items from the space data table.",
           "items": {
            "type": "string",
            "format": "json-pointer"
           }
          },
          "PartOf": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to another Zone item on this data table to represent that this item is a subset of that one. For example, a large zone for the west wing of a facility could be divided up into smaller zones that are part of the west wing zone.",
           "examples": [
            "Space/105"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Type": {
       "type": "array",
       "description": "Represents information related to the different types of products and equipment in the Facility.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Description",
          "Manufacturer_Ref",
          "ModelNumber",
          "WarrantyGuarantorParts_Ref",
          "WarrantyDurationParts",
          "WarrantyGuarantorLabor_Ref",
          "WarrantyDurationLabor",
          "WarrantyDurationUnit"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the asset Type.",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the asset Type.",
           "examples": [
            "32x80 Hollow core door"
           ]
          },
          "Category": {
           "type": "string",
           "description": "The classification for the asset type. This data field value comes from one of the values in COBie.PickList.Type.Category data field.",
           "examples": [
            "23-33 11 22 Electric Boilers",
            "Pr_60_60_08_27 Electric Boilers"
           ]
          },
          "AssetType": {
           "type": "string",
           "enum": [
            "Fixed",
            "Moveable"
           ],
           "description": "The type of asset. This data field value comes from one of the values in COBie.PickList.Type.AssetType data field.",
           "examples": [
            "Fixed",
            "Moveable"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "Manufacturer_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "The name of the company that manufactures the asset. This is a json-pointer reference to an entry in the COBie.Company table.",
           "examples": [
            "Company/26"
           ]
          },
          "ModelNumber": {
           "type": "string",
           "format": "json-pointer",
           "description": "During the construction and handover phases, this is the manufacturer’s model number of the installed product. During planning and design phases, this data field is not applicable",
           "examples": [
            "Mark IV v2"
           ]
          },
          "WarrantyGuarantorParts_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "During the construction and handover phases, this is the name of the company that is responsible for replacement parts during the warranty period. During planning and design phases, this data field is not applicable. This is a json-pointer reference to an entry in the COBie.Company table.",
           "examples": [
            "Company/27"
           ]
          },
          "WarrantyDurationParts": {
           "type": "string",
           "format": "json-pointer",
           "description": "During the construction and handover phases, this is the length of the warranty period for replacement parts provided by the product manufacturer. During planning and design phases, this data field is not applicable.",
           "examples": [
            "3",
            "36"
           ]
          },
          "WarrantyGuarantorLabor_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "During the construction and handover phases, this is the name of the company that is responsible for labor costs during the warranty period. During planning and design phases, this data field is not applicable. This is a json-pointer reference to an entry in the COBie.Company table.",
           "examples": [
            "Company/28"
           ]
          },
          "WarrantyDurationLabor": {
           "type": "string",
           "format": "duration",
           "description": "During the construction and handover phases, this is the length of the warranty period for labor repairs provided by the product manufacturer. During planning and design phases, this data field is not applicable.",
           "examples": [
            "1",
            "12"
           ]
          },
          "WarrantyDurationUnit": {
           "type": "string",
           "enum": [
            "As required",
            "Day",
            "Minute",
            "Month",
            "Quarter",
            "Week",
            "Year"
           ],
           "description": "The unit of measure associated with values found in COBie.Type.WarrantyDurationParts and COBie.Type.WarrantyDurationLabor. If allowable values are not specified by contract, the default values are Month and Year. This data field value comes from one of the values in COBie.PickList.Units.Duration data field."
          },
          "ModelReference": {
           "type": "string"
          },
          "NominalHeight": {
           "type": "number"
          },
          "NominalLength": {
           "type": "number"
          },
          "NominalWeight": {
           "type": "number"
          },
          "NominalWidth": {
           "type": "number"
          },
          "PurchaseCost": {
           "type": "string",
           "description": "The purchase cost of the asset."
          },
          "WarrantyDescription": {
           "type": "string",
           "description": "A description of the warranty for the asset."
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Component": {
       "type": "array",
       "description": "The individual instances of the products and equipment define in the Type data table.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Description",
          "Space_Ref"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the asset Component.",
           "description": "The name of the asset Component. This is the primary key for this data table and each value must be unique and must not contain a comma."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the asset Component."
          },
          "AssetIdentifier": {
           "type": "string"
          },
          "BarCode": {
           "type": "string"
          },
          "SerialNumber": {
           "type": "string"
          },
          "TagNumber": {
           "type": "string"
          },
          "Type_Ref": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to an item from the type data table."
          },
          "Space_Ref": {
           "type": "array",
           "format": "json-pointer",
           "description": "A json-pointer reference to an item from the space data table."
          },
          "SecondarySpace_Ref": {
           "type": "array",
           "minItems": 1,
           "description": "An array of json-pointer references to items from the space data table.",
           "items": {
             "type": "string",
             "format": "json-pointer",
            }
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "InstallationDate": {
           "type": "string",
           "format": "date"
          },
          "WarrantyStartDate": {
           "type": "string",
           "format": "date"
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "System": {
       "type": "array",
       "description": "Systems represent aggregations of Components that provide some common function.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Component_Ref"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the System.",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the System.",
           "examples": [
            "East wing HVAC"
           ]
          },
          "Category": {
           "type": "string",
           "description": "The classification for the System. This data field value comes from one of the values in COBie.PickList.System.Category data field.",
           "examples": [
            "21-04 20 10 Domestic Water Distribution",
            "EF_55_70 Water supply"
           ]
          },
          "Component_Ref": {
           "type": "array",
           "minItems": 1,
           "description": "An array of json-pointer references to items from the component table.",
           "items": {
            "type": "string",
            "format": "json-pointer"
           },
           "examples": [
            [
             "Component/105",
             "Component/237"
            ]
           ]
          },
          "PartOf": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to another System item on this data table to represent that this item is a subset of that one. For example, a large zone for the west wing of a facility could be divided up into smaller zones that are part of the west wing zone.",
           "examples": [
            "System/105"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Resource": {
       "type": "array",
       "description": "Resource records identify the tools, materials, and training needed to maintain the facility, structure, or group of structures.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the Resource.",
           "description": "The name of the Resource that is required to be used on the Job. This Resource may be shared across multiple Jobs. This is the primary key for this data table and each value must be unique and must not contain a comma."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Resource.",
           "examples": [
            "T8 warm white florescent tubes – 4ft"
           ]
          },
          "Category": {
           "type": "string",
           "enum": [
            "Labor",
            "Material",
            "Tools",
            "Training"
           ],
           "description": "The classification for the Resource. This data field value comes from one of the values in COBie.PickList.Resource.Category data field.",
           "examples": [
            "Labor",
            "Material"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC
           entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          }
         },
         “additionalProperties”: {
          "type": "string"
         }
        }
       ]
      },
      "Job": {
       "type": "array",
       "description": "Identifies the variety of work that is required to operate, maintain, start up, shut down, or troubleshoot a given Component in the facility, structure, or group of structures.",
       "items": [
        {
         "type": "object",
         "required": [
          "Name",
          "Description",
          "Duration",
          "DurationUnit",
          "Interval",
          "IntervalUnit",
          "Priors",
          "Resource_Ref"
         ],
         "properties": {
          "Name": {
           "type": "string",
           "title": "The name of the Job.",
           "description": "This is the primary key for this data table and each must be unique."
          },
          "Description": {
           "type": "string",
           "description": "A general text description of the Job."
          },
          "TaskNumber": {
           "type": "string"
          },
          "Category": {
           "type": "string",
           "enum": [
            "Adjustment",
            "Calibration",
            "Emergency",
            "Inspection",
            "Operation",
            "Project Management",
            "Safety",
            "ShutDown",
            "StartUp",
            "Testing",
            "Trouble"
           ],
           "description": "The classification for the Job. This data field value comes from one of the values in COBie.PickList.Job.Category data field.",
           "examples": [
            "Inspection",
            "ShutDown"
           ]
          },
          "Status": {
           "type": "string",
           "enum": [
            "Not Yet Started",
            "Started",
            "Completed"
           ],
           "description": "Status of the job.",
           "examples": [
            "Not Yet Started",
            "Completed"
           ]
          },
          "Table_Ref": {
           "type": "array",
           "minItems": 1,
           "description": "An array of json-pointer references to items from other tables that are part of the job.",
           "items": {
            "type": "string",
            "format": "json-pointer"
           },
           "examples": [
            [
             "Company/21",
             "Space/105",
             "Component/237"
            ]
           ]
          },
          "PartOf": {
           "type": "string",
           "format": "json-pointer",
           "description": "A json-pointer reference to another Job item on this table to represent that this item is a subset of that one. For example, adding a reusable sub-task such as shutdown to a larger job such as inspection.",
           "examples": [
            "Space/105"
           ]
          },
          "ExtIdentifier": {
           "type": "string",
           "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
           "examples": [
            "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
           ]
          },
          "ExtObject": {
           "type": "string",
           "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
           "examples": [
            "IfcSpace"
           ]
          },
          "ExtSystem": {
           "type": "string",
           "description": "The name of the computer system generating the row of COBie data.",
           "examples": [
            "Autodesk Revit 2023, Build: 20220429_1500(x64)",
            "ArchiCAD 19 Full (USA) / Build: 5005",
            "IBM Maximo"
           ]
          },
          "Duration": {
           "type": "number"
          },
          "DurationUnit": {
           "type": "string",
          "enum": [
           "Day",
           "Minute",
           "Month",
           "Quarter",
           "Week",
           "Year"
          ],
          "description": "The unit of measure associated with values found in COBie.Job.Duration. If allowable values are not specified by contract, the default values are Month and Year. This data field value comes from one of the values in COBie.PickList.Units.Duration data field."
         },
         "Interval": {
          "type": "string"
         },
         "IntervalUnit": {
          "type": "string",
          "enum": [
           "As required",
           "Day",
           "Minute",
           "Month",
           "Quarter",
           "Week",
           "Year"
          ]
         },
         "Priors": {
          "type": "array",
          "minItems": 1,
          "description": "An array of json-pointer references to items from the TaskNumber field of the Job table.",
          "items": {
            "type": "string",
            "format": "json-pointer"
          },
          "examples": [
              [
                "Resource/2108",
                "Resource/237"
              ]
            ]
          }
         "Resource_Ref": {
          "type": "array",
          "minItems": 1,
          "description": "An array of json-pointer references to items from the Resource table that are part of the job.",
          "items": {
           "type": "string",
           "format": "json-pointer"
          },
          "examples": [
           [
            "Resource/2108",
            "Resource/237"
           ]
          ]
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       }
      ]
     },
     "Event": {
      "type": "array",
      "description": "Events represent a single occurrence of a task as part of a Job.",
      "items": [
       {
        "type": "object",
        "required": [
         "Name",
         "Description",
         "StartDate"
        ],
        "properties": {
         "Name": {
          "type": "string",
          "title": "The name of the Event.",
          "description": "The name of the Event. This value does not need to be unique."
         },
         "Description": {
          "type": "string",
          "description": "A general text description of the Event."
         },
         "Category": {
          "type": "string",
          "enum": [
           "One Time",
           "Planned",
           "Repeating"
          ],
          "description": "The classification for the Event. This data field value comes from one of the values in COBie.PickList.Event.Category data field.",
          "examples": [
           "One Time",
           "Planned",
           "Repeating"
          ]
         },
         "Company_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Company/3"
          ]
         },
         "Jpb_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Job/11"
          ]
         },
         "Table_Ref": {
          "type": "array",
          "minItems": 1,
          "description": "An array of json-pointer references to items from other tables that are part of the event.",
          "items": {
           "type": "string",
           "format": "json-pointer"
          },
          "examples": [
           [
            "Company/21",
            "Space/105",
            "Component/237"
           ]
          ]
         },
         "ExtIdentifier": {
          "type": "string",
          "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
          "examples": [
           "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
          ]
         },
         "ExtObject": {
          "type": "string",
          "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are
          excluded) when transforming IFC data to a given row of COBie data.",
          "examples": [
           "IfcSpace"
          ]
         },
         "ExtSystem": {
          "type": "string",
          "description": "The name of the computer system generating the row of COBie data.",
          "examples": [
           "Autodesk Revit 2023, Build: 20220429_1500(x64)",
           "ArchiCAD 19 Full (USA) / Build: 5005",
           "IBM Maximo"
          ]
         },
         "StartDate": {
          "type": "string",
          "format": "date-time"
         },
         "EndDate": {
          "type": "string",
          "format": "date-time"
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       }
      ]
     },
     "Package": {
      "type": "array",
      "description": "Includes information about the legal contract that required the COBie deliverable.",
      "items": [
       {
        "type": "object",
        "required": [
         "Name",
         "Description",
         "StartDate"
        ],
        "properties": {
         "Name": {
          "type": "string",
          "title": "The name of the Package.",
          "description": "This is the primary key for this data table and each must be unique."
         },
         "Description": {
          "type": "string",
          "description": "A general text description of the Package."
         },
         "Category": {
          "type": "string",
          "description": "The classification for the Package. This data field value comes from one of the values in COBie.PickList.Package.Category data field."
         },
         "Company_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Company/3"
          ]
         },
         "Event_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Event/909"
          ]
         },
         "ExtIdentifier": {
          "type": "string",
          "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
          "examples": [
           "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
          ]
         },
         "ExtObject": {
          "type": "string",
          "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
          "examples": [
           "IfcSpace"
          ]
         },
         "ExtSystem": {
          "type": "string",
          "description": "The name of the computer system generating the row of COBie data.",
          "examples": [
           "Autodesk Revit 2023, Build: 20220429_1500(x64)",
           "ArchiCAD 19 Full (USA) / Build: 5005",
           "IBM Maximo"
          ]
         },
         "StartDate": {
          "type": "string",
          "format": "date-time"
         },
         "EndDate": {
          "type": "string",
          "format": "date-time"
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       }
      ]
     },
     "Risk": {
      "type": "array",
      "description": "Identifies the exchange of business process and exception reporting information related to other parts of a COBie deliverable.",
      "items": [
       {
        "type": "object",
        "required": [
         "Name",
         "Description",
         "Consequence",
         "LevelOfRisk",
         "Likelihood"
        ],
        "properties": {
         "Name": {
          "type": "string",
          "title": "The name of the Risk.",
          "description": "This is the primary key for this data table and each must be unique."
         },
         "Description": {
          "type": "string",
          "description": "A general text description of the Risk."
         },
         "Category": {
          "type": "string",
          "enum": [
           "Change",
           "Claim",
           "Coordination",
           "Environmental",
           "Function",
           "IndoorAirQuality",
           "Installation",
           "RFI",
           "Safety",
           "Specification"
          ],
          "description": "The classification for the Risk. This data field value comes from one of the values in COBie.PickList.Risk.Category data field.",
          "examples": [
           [
            "Environmental",
            "Safety"
           ]
          ]
         },
         "Spatial_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Space/909"
          ]
         },
         "Physical_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Component/909"
          ]
         },
         "Process_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Event/909"
          ]
         },
         "ExtIdentifier": {
          "type": "string",
          "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
          "examples": [
           "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
          ]
         },
         "ExtObject": {
          "type": "string",
          "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
          "examples": [
           "IfcSpace"
          ]
         },
         "ExtSystem": {
          "type": "string",
          "description": "The name of the computer system generating the row of COBie data.",
          "examples": [
           "Autodesk Revit 2023, Build: 20220429_1500(x64)",
           "ArchiCAD 19 Full (USA) / Build: 5005",
           "IBM Maximo"
          ]
         },
         "Company_Ref": {
          "type": "string",
          "format": "json-pointer",
          "examples": [
           "/Company/3"
          ]
         },
         "Consequence": {
          "type": "string",
          "enum": [
           "Very High",
           "High",
           "Moderate",
           "Low",
           "Unknown"
          ]
         },
         "LevelOfRisk": {
          "type": "string",
          "enum": [
           "Very High",
           "High",
           "Moderate",
           "Low",
           "Unknown"
          ]
         },
         "Likelihood": {
          "type": "string",
          "enum": [
           "Has Occurred",
           "High",
           "Moderate",
           "Low",
           "Unknown"
          ]
         },
         "Mitigation": {
          "type": "string"
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       }
      ]
     },
     "Document": {
      "type": "array",
      "description": "Document records identify external files that provide information associated with data in a COBie deliverable.",
      "items": [
       {
        "type": "object",
        "required": [
         "Name",
         "Description",
         "Table_Ref",
         "ApprovalBy",
         "Path"
        ],
        "properties": {
         "Name": {
          "type": "string",
          "title": "The name of the Document.",
          "description": "The name of the Document. This value does not need to be unique."
         },
         "Description": {
          "type": "string",
          "description": "A general text description of the Document."
         },
         "Category": {
          "type": "string",
          "enum": [
           "Certificates",
           "Client Requirements",
           "Closeout Submittals",
           "Contract Drawings",
           "Contract Modifications",
           "Contract Specifications",
           "Design Data",
           "Design Review Comment",
           "Manufacturer Field Reports",
           "Manufacturer Instructions",
           "Operation and Maintenance",
           "Preconstruction Submittals",
           "Product Data",
           "Punch List Items",
           "Request for Information",
           "Requests for Information",
           "Samples",
           "Shop Drawings",
           "Specifications",
           "Test Reports"
          ],
          "description": "The classification for the Document. This data field value comes from one of the values in COBie.PickList.Document.Category data field.",
          "examples": [
           "Contract Drawings",
           "Specifications"
          ]
         },
         "Table_Ref": {
          "type": "string",
          "format": "json-pointer",
          "description": "The element to which the document applies.",
          "examples": [
           "/Event/909"
          ]
         },
         "ExtIdentifier": {
          "type": "string",
          "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
          "examples": [
           "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
          ]
         },
         "ExtObject": {
          "type": "string",
          "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
          "examples": [
           "IfcSpace"
          ]
         },
         "ExtSystem": {
          "type": "string",
          "description": "The name of the computer system generating the row of COBie data.",
          "examples": [
           "Autodesk Revit 2023, Build: 20220429_1500(x64)",
           "ArchiCAD 19 Full (USA) / Build: 5005",
           "IBM Maximo"
          ]
         },
         "ApprovalBy": {
          "type": "string"
         },
         "Path": {
          "type": "string",
          "format": "uri"
         },
         "File": {
          "type": "string",
          "examples": [
           "123Main_Arch_R23.rvt",
           "ComissioningReport.pdf",
           "n/a"
          ]
         },
         "Reference": {
          "type": "string"
         }
        },
        “additionalProperties”: {
         "type": "string"
        }
       }
      ]
     },
     "Attribute": {
      "type": "array",
      "description": "Used to store custom data fields for the COBie deliverable.",
      "items": [
       {
        "type": "object",
        "required": [
         "Name",
         "Table_Ref",
         "type",
         "Unit"
        ],
        "properties": {
         "Name": {
          "type": "string",
          "title": "The name of the Attribute.",
          "description": "The name of the Attribute. This value does not need to be unique."
         },
         "Description": {
          "type": "string",
          "description": "A general text description of the Attribute."
         },
         "Category": {
          "type": "string",
          "description": "The classification for the Attribute."
         },
         "Table_Ref": {
          "type": "string",
          "format": "json-pointer",
          "description": "The element to which the attribute applies.",
          "examples": [
           "/Space/42"
          ]
         },
         "ExtIdentifier": {
          "type": "string",
          "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
          "examples": [
           "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
          ]
         },
         "ExtObject": {
          "type": "string",
          "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
          "examples": [
           "IfcSpace"
          ]
         },
        "ExtSystem": {
         "type": "string",
         "description": "The name of the computer system generating the row of COBie data.",
         "examples": [
          "Autodesk Revit 2023, Build: 20220429_1500(x64)",
          "ArchiCAD 19 Full (USA) / Build: 5005",
          "IBM Maximo"
         ]
        },
        "Value": {
         "type": "string",
         "examples": [
          "123",
          "1200.56"
         ]
        },
        "Unit": {
         "type": "string",
         "examples": [
          "meter"
         ]
        },
        "AllowedValues": {
         "type": "string",
         "description": "A comma separated list of one or more allowed values for the “Value” data field of a particular item on the “Attribute” data table.",
         "examples": [
          "Inlet, Outlet",
          "5kVA, 10kVA, 15kVA",
          "Fixed, Variable",
          "n/a"
         ]
        }
       },
       “additionalProperties”: {
        "type": "string"
       }
      }
     ]
    },
    "Coordinate": {
     "type": "array",
     "description": "Represents the simple geometric information associated with data in a COBie deliverable.",
     "items": [
      {
       "type": "object",
       "required": [
        "Name",
        "Table_Ref",
        "CoordinateXAxis",
        "CoordinateYAxis",
        "CoordinateZAxis",
        "ClockwiseRotation",
        "ElevationalRotation",
        "YawRotation"
       ],
       "properties": {
        "Name": {
         "type": "string",
         "title": "The name of the Coordinate.",
         "description": "The name of the Coordinate. This value does not need to be unique."
        },
        "Category": {
         "type": "string",
         "enum": [
          "Point",
          "Line-end-one",
          "Line-end-two",
          "Box-lowerleft",
          "Box-upperright"
         ],
         "description": "The classification for the Coordinate. This data field value comes from one of the values in COBie.PickList.Coordinate.Category data field."
        },
        "Table_Ref": {
         "type": "string",
         "format": "json-pointer",
         "description": "The element to which the coordinate applies.",
         "examples": [
          "/Space/42"
         ]
        },
        "ExtIdentifier": {
         "type": "string",
         "description": "The unique identifier of the identified ExternalObject that would allow COBie data to be matched back to the data from which it was developed in the named ExternalSystem. This might be a GUID or ElementID.",
         "examples": [
          "4ec17585-c36e-4cc3-8301-61df48a06d7e-000c89be"
         ]
        },
        "CoordinateXAxis": {
         "type": "number"
        },
        "CoordinateYAxis": {
         "type": "number"
        },
        "CoordinateZAxis": {
         "type": "number"
        },
        "ClockwiseRotation": {
         "type": "number"
        },
        "ElevationalRotation": {
         "type": "number"
        },
        "YawRotation": {
         "type": "number"
        },
        "RelativeTo": {
         "type": "string"
        },
        "ExtObject": {
         "type": "string",
         "description": "The name of the data object within the computer system that holds the data provided in a given row of COBie data. The default values are the associated IFC entities that are mapped (and those that are excluded) when transforming IFC data to a given row of COBie data.",
         "examples": [
          "IfcSpace"
         ]
        },
        "ExtSystem": {
         "type": "string",
         "description": "The name of the computer system generating the row of COBie data.",
         "examples": [
          "Autodesk Revit 2023, Build: 20220429_1500(x64)",
          "ArchiCAD 19 Full (USA) / Build: 5005",
          "IBM Maximo"
         ]
        }
       },
       “additionalProperties”: {
        "type": "string"
       }
      }
     ]
    }
   }
  }

This section details the changes to the COBie V3 Standard from the previous V2.4 standard.

Version 3 of the COBie standard incorporates 61 different changes and updates grouped into the following four categories.

Ease of Use

• More concise documentation
• Removal of data tables rarely used
• Renaming of data fields and headers to better understand their purpose
• Resorting of headers to better group them
• New “Title Block” section to have all pertinent deliverable information in one place

Modernization

• Removal of personally identifiable information data fields
• Replacing “Floor” data table with “Level” data table to accommodate infrastructure projects
• Support for JSON format for machine-to-machine exchanges

Capabilities

• Adding new “PartOf“ data field on asset data tables to better understand relationships
• Adding data fields that accommodate classifying and geo-locating projects better
• Adding a new “SpaceType” data table to better organize spaces

Workflow

• Adding data tables to better document the activities of a facility (especially useful for handover between owners)
• New “Package”, “Event”, and “Risk” data tables to go along with the existing “Job” data table

This data table was overhauled to include much more information pertinent to the COBie submittal. Dubbed the “Title Block”, the data fields now in this data table are a combination of new and moved from other data tables.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table.

FIGURE AD.2

This data table is no longer about individuals, but about companies/organizations.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.3

This data table was revamped to not limit it to buildings.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.4

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.5

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.6

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.7

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.8

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.9

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.10

No changes to this data table except the changes that affect every data table, including removing the “CreatedBy” and “CreatedOn” data fields and reorganizing the data fields.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.11

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.12

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.13

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.14

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.15

This data table has been repurposed to focus on the risks that can be associated with Jobs (existing data table) and Events (new data table), such as those related to health and safety.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.16

Many changes took place to align this data table with the changes to the other data tables, including adding, removing, and renaming of different data tables.

The figure below shows the comparison between the data fields in V2.4 and those in V3 for this data table. The gray text along the top of V3 does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.17

This is a new data table that allows Spaces to belong to a type, not just a classification. For example, “Office”, “Mechanical”, "Circulation", etc.

The figure below shows the data fields for this new data table. The gray text along the top does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.18

This is a new data table that allows the documentation of events that affect a facility. An event is a component or an instance of a Job (existing data table).

The figure below shows the data fields for this new data table. The gray text along the top does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.19

This is a new data table that captures a record of who is responsible and is often referred to as a “work package.” Multiple Jobs (existing data table) and Events (new data table) can be associated with these responsible parties.

The figure below shows the data fields for this new data table. The gray text along the top does not display in the data tables and is shown to better understand the new organization of the data fields.

FIGURE AD.20