06 Quick Start Guide - Definitions.pdf

U.S. General Services Administration

COBie Requirements Specification

January 2019

COBie Requirements Specification U.S. General Services Administration

Contact Definition A tab in the COBie spreadsheet. Each row in the Contact tab identifies a person or company referenced elsewhere in a COBie spreadsheet. Con-tact.Email is the unique identifier for this tab.

Required Beginning in Final Concept Design Phase QC Checks 1. Tab must have at least one row

Contact.Email Definition A well-formed email address used to identify this specific Contact.

Example Value “Bob.Builder@ConstructionCo.com” Required Beginning in Final Concept Design Phase QC Checks 1. Must be unique within the scope of the tab

2. Must have a text value that is not n/a or empty

3. Must be a valid email address

Contact.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Contact.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

GSA COBie Requirements Specification

This specification details the GSAs COBie requirement for designers and constructors. It should be used by ODC project managers to specify requirements in contracts, and by OFM personnel to check in-progress handover deliverables during design, throughout construction, and at turnover.

Contact Tab

Contact.Category Definition The category of business in which the specific Contact is engaged. Must be a predefined value list found in the Contact.Category PickList.

Example Value “34-35 15 11: Contractor” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value from list in Contact.Category Picklist

Contact.Company Definition The name of the company for the Contact. If Contact.Category = Man-ufacturer then must match value in the Contact.Company Picklist.

Example Value “Construction Co Inc.”

Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. If Contact.Category = Manufacturer then must match value in the Contact.Company Picklists

Contact.Phone Definition The telephone number for the Contact.

Example Value “(555) 555-5558” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

Contact.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.Department (optional) Definition The name of the department for the Contact.

Example Value “BIM Program” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.OrganizationCode (optional) Definition The organizational code for the Contact.

Example Value “PCL#123” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.GivenName Definition If the Contact is a person, the given name of the Contact.

Example Value “Allison” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.FamilyName Definition If the Contact is a person, the family name of the Contact.

Example Value “Harper” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.Street (optional) Definition The street address for the Contact Example Value “1005 N. Glebe Rd” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.PostalBox (optional) Definition The postal box address for the Contact.

Example Value “3022” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.Town (optional) Definition The city or town address for the Contact.

Example Value “Arlington” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.StateRegion (optional) Definition The state or regional address for the Contact.

Example Value “VA” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.PostalCode (optional) Definition The zip or postal code, address for the Contact.

Example Value “22201” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Contact.Country (optional) Definition The country for the Contact.

Example Value “USA” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility Definition A tab in the COBie spreadsheet. There may only be one row in the facility tab. Projects composed of multiple facilities, shall be described by separate COBie spreadsheets. Facility.Name is the primary key for this tab.

Required Beginning in Final Concept Design Phase QC Checks 1. Only one facility is allowed

Facility.Name Definition The GSA Building Number, or if one is not yet available the name of the Facility as it appears on design drawings Example Value “DC000ZZ” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be unique within the scope of the tab

Facility.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Facility.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Facility.Category Definition The classification of the facility described by function. Must match a value found in the list in the Facility.Category Picklist.

Example Value “11-27 38 11: Government Office Building” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value from list in Facility.Category Picklist

Facility

Facility.ProjectName Definition The name of the Project as it appears in ePM.

Example Value “DC FEDERAL CENTER” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

Facility.SiteName Definition The name of the Site as it appears on design drawings, or as otherwise specified by contract.

Example Value “DC FEDERAL CENTER” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

Facility.LinearUnits Definition The associated unit of measurement applied to all Linear information in the COBie Spreadsheet. Acceptable values are “FT: FOOT/FEET”, “FUR: Furlong”, “IN: Inch”, “INCH: Inches”, “LF: Linear Foot”, “MI:

Miles”, “YD: Yard”, “HM: Hectometer”, “M: Meter”, “MM: Milimeter”, “CM: Centimeters”, “DAM: Dekameter”, or “DM: Decimeter” as listed in the Facility.LinearUnits Picklist

Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in Facility.LinearUnits Picklist

Facility.AreaUnits Definition The associated unit of measurement applied to all Area information in the COBie Spreadsheet. Acceptable values are “AC: Acre”, “SQ.FT.:

Square Feet”, “SQ.IN.: Square Inch”, “SQ.MI.: Square Miles” ,”SQ.YD.:

Square Yards”, “SQ.CM.: Square Centimeter”, “SQ.KM.: Square Kilome-ters”, “SQ.M: Square Meter”, or “SQ.MM.: Square Millimeter”, as listed in the Facility.AreaUnit Picklist.

Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in the Facility.AreaUnit Picklist

Facility.VolumeUnits Definition The associated unit of measurement applied to all Volume information in the COBie Spreadsheet. Acceptable values are “CU.FT.: Cubic Foot”, “CU.IN.: Cubic Inch”, “CU.YD.: Cubic Yard”, “GL: GALLON”, “OZ: Ounce”, “PT: Pint”, “QT: Quart”, “TCF:

Trillion Cubic Feet”, “CU. MM.: Cubic Millimeter”, “CU.CM.: Cubic Centimeter”, “CU.M.: Cubic Meter”, “G: Gram”, “L: Liter”, “LITERS:

Liters”, “ML: Mililiter”, “TSP: Teaspoon” as shown in the VolumeUnit Picklist.

Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in the VolumeUnit Picklist

Facility.CurrencyUnit Definition The associated unit of measurement applied to all COBie information other than that found in the Attribute and Impact worksheets.

Example Value “Dollars” Required Beginning in Final Concept Design Phase

Facility.AreaMeasurement Definition The associated measurement method used to calculate spatial area infor-mation in the COBie Spreadsheet.

Example Value “Autodesk Revit Architecture 2016 BIM Area” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

Facility.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalProjectObject Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “ifcProject” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalProjectIdentifier Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “3eM8WbY_59RR5TDWry5aRV” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalSiteObject Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “IfcSite” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalSiteIdentifier Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “3eM8WbY_59RR5TDWry5aRT” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalFacilityObject Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “IfcBuilding” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ExternalFacilityIdentifier Definition For information originating in IFC models this information is an ad-ditional object identifier, allowing information about this Facility to be referenced back to the computer software that initially generated that Information.

Example Value “57ed7869-1bb7-4165-a158-0a902dcb47fd” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.Description (optional) Definition A general text description of the facility.

Example Value “A 5-story class A office building” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.ProjectDescription (optional) Definition A general text description of the project.

Example Value “Construction of a ~350,000 SF building. CIP concrete structure with curtain wall.”

Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.SiteDescription (optional) Definition A general text description of the site.

Example Value “2.5 Acres” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Facility.Phase (optional) Definition The designation of the phase of the project reflected in a given COBie data set.

Example Value “As-Built” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Floor Definition A tab in the COBie spreadsheet. Floors are the vertical levels of a verti-cal facility. Geographic areas, such as a facility’s site, may also be identi-fied on the floor tab. Floor.Name is the primary key for this tab.

Required Beginning in Final Concept Design Phase QC Checks 1. Tab must have at least one row

Floor.Name Definition The name of the floor as it appears on other contract documents, such as design drawings.

Example Value “Basement 1st Floor” Required

QC Checks 1. Must have a text value that is not n/a or empty

2. Must be unique within the scope of the tab

Floor.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Floor.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Floor.Category Definition A classification of the type of information contained within one row.

Must match values found in the Floor.Category Picklist.

Example Value “Basement, 1st Level” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match values found in the Floor.Category Picklist

Floor

Floor.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Floor.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Floor.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Floor.Description (optional) Definition A general text description of the floor.

Example Value “10” CIP Slab, rough finish” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Floor.Elevation (optional) Definition Elevation at the top of the floor structure. If allowable values are not specified by contract, the default value is measured as a relative value compared to the facilities datum.

Example Value “6080” Required Beginning in Final Concept Design Phase QC Checks 1. Must represent valid number greater than zero or ‘n/a’

Floor.Height (optional) Definition Distance between top of floor structure to bottom of structure above.

Typically applicable to rows having the Floor.Category of “Floor”.

Example Value “3040” Required Beginning in Final Concept Design Phase QC Checks 1. Must represent valid number greater than zero or ‘n/a’

Space Definition A tab in the COBie spreadsheet. Spaces are the horizontal decomposi-tion of floors into areas which have common functional purpose and use. Vertically, spaces run from top of floor to bottom of slab above.

Occupied space runs to bottom of the ceiling as expressed by Space.

UsableHeight. Large Spaces which have more than a single functional purpose or user may be separated into individual spaces. Spaces may also be used on floors of type “Roof ” or “Site” to identify spatial regions outside a facility enclosure. Space.Name is the primary key for this tab.

Required Beginning in Design Development Phase QC Checks 1. Tab must have at least one row

Space.Name Definition The Space.Name must match the value found on design drawings at the equivalent project stage of the current deliverable. Only the room num-ber should be included for this value (e.g. “1002).

Example Value “1002” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

Space.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Space.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Space

Space.Category Definition The category of space described by the COBie data set. If allowable values are not specified by contract, the default value for this information is the current OmniClass Table 13.

Example Value “13-55 29 21 11: Conference Room” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

Space.FloorName Definition A foreign key identifying the COBie.Floor.Name.

Example Value “Basement 1st Level” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in Floor.Name

Space.Description Definition The description of the space found on design drawings at the equivalent project stage of the current deliverable. It should not include room num-ber values as this can lead to duplicated data.

Example Value “CONFERENCE” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must not include room number values

Space.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Space.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Space.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Space.RoomTag Definition Signage provided for each space. Signage applied to doors, if different, is identified as Attribute records related to each applicable door. The information here is equivalent to that found in construction signage submittals.

Example Value “101” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Space.UsableHeight (optional) Definition Distance from top of finished floor to bottom of ceiling. If there is no ceiling then this value must match Floor.Height.

Example Value “8” Required Beginning in Design Development Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Space.GrossArea (optional) Definition Total space area as specified in the design contract and calculated by the identified Facility.AreaMeasurement.

Example Value “267” Required Beginning in Design Development Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Space.NetArea (optional) Definition Usable space areas as specified in the design contract and calculated by the identified Facility.AreaMeasurement Example Value “250” Required Beginning in Design Development Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Zone Definition A tab in the COBie spreadsheet. Zones are aggregations of spaces that provide some common purpose. Zone.Name, Zone.Category, and Zone.

SpaceName provide the compound key for this tab.

Required Beginning in Final Concept Design Phase QC Checks

Zone.Name Definition The name of the specific function performed by a group of spaces with-in a given area of the building.

Example Value “Mechanical Zone” Required Beginning in Final Concept Design Phase QC Checks 1. Must have a text value that is not n/a or empty

Zone.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Zone.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Zone.Category Definition A foreign key identifying the COBie.Space.Name. The plural designa-tion of “SpaceNames” indicating use of a delimited list of Space.Name values.

Example Value “B1002” Required Beginning in Final Concept Design Phase QC Checks 1. Must match values found in Space.Name

Zone

Zone.SpaceNames Definition A foreign key identifying the COBie.Space.Name. The plural designa-tion of “SpaceNames” indicating use of a delimited list of Space.Name values.

Example Value “B1002” Required Beginning in Final Concept Design Phase QC Checks 1. Must match values found in Space.Name

Zone.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Zone.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Zone.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Zone.Description (optional) Definition A general text description of the zone.

Example Value “Ventilation” Required Beginning in Design Development Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Zone

Type Definition A tab in the COBie spreadsheet. Types are the different products and equipment to be installed in the facility. Type.Name is the primary key for this tab.

Required Beginning in Construction Documents Phase QC Checks 1. Tab must have at least one row

Type.Name Definition The Type.Name must match the value found on design drawing sched-ules at the equivalent project stage of the current deliverable.

Example Value “Air Handling Unit” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Type.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Type.Category Definition The category of type described by the COBie data set. The default value is the GSA FACTS Code, which can be found in the Type.category Picklist.

Example Value “D304008.09.01” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match value found in the Type.category Picklist

Type

Type.Description Definition A general text description of the type. If description is present on design drawings schedules, this value must match. Do not include a reiteration of the Type.Name value

Example Value “Air Handling Unit, Up to 10 Tons” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (n/a is acceptable)

2. If description is present on design drawing schedules, this value must match

3. Must not include value from Type.Name

Type.AssetType Definition Type A classification of the asset within one row. If allowable values are not specified by contract, the default values are: “Fixed” and “Movable”.

Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.Manufacturer Definition During construction and handover phase: the Contact.Email of the installed product. During planning and design phase: not applicable.

Example Value “trane@trane.com” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in Contact.Email

Type.ModelNumber Definition During construction and handover phase: the manufacturer’s model number of the installed product. During planning and design phase: not applicable.

Example Value “CSAA” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.WarrantyGuarantorParts Definition During construction and handover phase: the Contact.Email of the party, or parties, responsible for replacement parts during the warranty period. During planning and design phase: not applicable.

Example Value “trane@trane.com” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in the Contact.Company field

Type.WarrantyDurationParts Definition During construction and handover phase: the length of the warranty period for replacement parts provided by the product manufacturer.

During planning and design phase: not applicable.

Example Value “2” Required Beginning in Construction Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Type.WarrantyGuarantorLabor Definition During construction and handover phase: the Contact.Email of the party, or parties, responsible for labor costs during the warranty period.

Typically the same as Type.WarrantyGuarantorParts. During planning and design phase: not applicable.

Example Value “Bob.Builder@ConstructionCo.com” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in Contact.Email

Type.WarrantyDurationLabor Definition During construction and handover phase: the length of the warranty period for labor repairs provided by the product manufacturer. Typically the same as Type.WarrantyDurationParts. During planning and design phase: not applicable.

Example Value “10” Required Beginning in Construction Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Type.WarrantyDurationUnit Definition The identification of the unit of measure associated with values found in

Type.WarrantyDurationParts and Type.WarrantyDurationLabor. If allow-able values are not specified by contract, the default values are: “month” and “year”.

Example Value “year” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.ReplacementCost (optional) Definition During construction and handover phase: The manufacturer’s suggested retail price for this type. During planning and design phase: not applica-ble.

Example Value “15,000” Required By Substantial Completion QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Type.ExpectedLife Definition During handover phase: the expected service life of the product type given the level of service within the facility. During planning, design, and construction phase: left blank unless conducting total cost of ownership studies.

Example Value “10” Required By Substantial Completion QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Type.DurationUnit Definition The identification of the unit of measure associated with value found in

Type.ExpectedLife. The default values are: “month” and “year”.

Example Value “years” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.WarrantyDescription (optional) Definition A general text description of the warranty.

Example Value “A two year parts warranty by the manufacturer, and two year warranty labor by the General Contractor.”

Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.NominalLength Definition An approximate measure of the bounding box surrounding the product type.

Example Value “.5” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.NominalWidth Definition An approximate measure of the bounding box surrounding the product type.

Example Value “.75” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Type.NominalHeight Definition An approximate measure of the bounding box surrounding the product type.

Example Value “.1” Required Beginning in Construction Phase QC Checks 1. If text is provided it must represent a valid number greater than zero or n/a

Type.ModelReference (optional) Definition The manufacturer’s catalog or reference resource, such as - website, where information about the installed product type may be found.

Example Value “www.trane.com/AHU/ProductInfo/notarealwebsitebutyougettheidea” Required Beginning in Construction Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Shape (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Requires 18” clearance on all sides for maintenance” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Size (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “450x450x300” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Color (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Silver” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Finish (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Paint” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Grade (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “1/12 grade” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Material (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Steel” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Constituents (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Product must be mounted 6” from other equipment to ensure proper ventilation”

Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.Features (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Includes mounting brackets that are compatible with 1-5/8" x 1-5/8" slotted unistrut channel”

Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.AccessibilityPerformance (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Should be mounted 33” to 36” above finished floor” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.CodePerformance (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Fire rating must match or exceed that of the wall in which the product is installed”

Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Type.SustainabilityPerformance (optional) Definition During planning and design phase: specific constraints that should be/ have been considered during the - specification process. During construc-tion and handover phase: the text description of associated - information found on a product manufacturers product data sheet.

Example Value “Must be R45 or greater” Required During All Phases QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Component Definition A tab in the COBie spreadsheet. Components are the individual instances of the products identified by Type. Component.Name is the primary key for this table.

Required Beginning in Construction Documents Phase QC Checks 1. Tab must have at least one row

Component.Name Definition The Component.Name must match the value found on design drawing schedules at the equivalent project stage of the current deliverable. For equipment scheduled by Type (and not Component) naming require-ments to ensure unique names for every component shall be specified by contract.

Example Value “AHU-001” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match the value found on design drawing schedules at the equivalent project stage of the current deliverable

Component.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Component.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Design Development Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Component

Component.TypeName Definition A foreign key identifying the COBie.Type.Name.

Example Value “Air Handling Unit” Required Beginning in Construction Documents Phase QC Checks 1. “Air Handling Unit”

Component.Space Definition A foreign key identifying the COBie.Space.Name. For components not contained in a single space, the value shall refer to the space from which the equipment is most likely to be maintained.

Example Value “1006” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a value in Space.Name

Component.Description Definition A general text description of the component.

Example Value “Air Handling Unit, Up to 10 Tons” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (n/a is acceptable)

2. If description is present on design drawing schedules, this value must match

Component.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Component.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Component.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

Component.SerialNumber Definition The serial number of the installed equipment. Component.SerialNumber must match the value found on installed equipment nameplates. During planning and design phase: not applicable.

Example Value “AH-250-PXL-3” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match the value found on installed equipment nameplates

Component.InstallationDate Definition The date on which the product or equipment was placed in its final loca-tion. During planning and design phase: not applicable. Must be in ISO Date format: “YYYY-MM-DDTHH:MM:SS”

Example Value “2019-01-25 16:00:03” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Component.WarrantyStartDate Definition The date on which the product or equipment was first powered. During planning and design phase: not applicable. Must be in ISO Date format:

“YYYY-MM-DD HH:MM:SS”

Example Value “2019-01-25 16:00:03” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Component.TagNumber (optional) Definition If a tag is required to be affixed to the product or equipment during construction, this value is the - designation for this product or equipment found on the associated tag. During planning and design phase: - not applicable. During planning and design phase: not applicable.

Example Value “AHU-15” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Component.BarCode (optional) Definition The bar code found on the installed product name plate. During planning and design phase: not - applicable.

Example Value “BC14529839t5” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

Component.AssetIdentifier (optional) Definition an alternative identifier for the specific component to be used as defined by associated contract.

Example Value “A1025467” Required Beginning in Construction Phase QC Checks 1. Must have a text value that is not n/a or empty

System Definition A tab in the COBie spreadsheet. Systems are aggregations of com-ponents that provide some common function. System.Name, System.

Category, and System.ComponentNames provide the compound key for this tab.

Required Beginning in Construction Documents Phase QC Checks

System.Name Definition The name of the specific function performed by a group of components within a given System.Category.

Example Value “Air Distribution System-001” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

System.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

System.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

System.Category Definition The category of the system described by the COBie data set. If allowable values are not specified by contract, the default value for this information is the current OmniClass Table 21.

Example Value “21-04 30 50 50: HVAC Air Distribution” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

System

System.ComponentNames Definition A foreign key identifying the COBie.Component.Name. The plural designation of “ComponentNames” indicating use of a delimited list of Component.Name values is depreciated in COBie version 2.4 in favor of the use of a single row for each System.Component.

Example Value “Chiller-001” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value that is not n/a or empty

2. Must match values found in Component.Name

System.ExternalSystem Definition If applicable, the name of the computer system generating the row of

COBie data.

Example Value “Autodesk Revit Architecture 2016” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

System.ExternalObject Definition If applicable, the name of the data object within the computer system that holds the data provided in a given row of COBie data.

Example Value “IfcOrganization” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

System.ExternalIdentifier Definition If applicable, the unique identifier of the external object that would allow COBie data to be matched back to the data in the named external system.

Example Value “ceceb95c-dd5b-4a75-98b7-cb1c754ababd” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

System.Description (optional) Definition A general text description of the system.

Example Value “Air Distribution - Forced air” Required Beginning in Construction Documents Phase QC Checks 1. Must have a text value (If not applicable, n/a is acceptable)

System

Spare Definition A tab in the COBie spreadsheet. Spare records identify the on-site spare parts, replacement parts, and lubricants needed to maintain the facility.

Spare.Name and Spare.TypeName form the compound key for this tab.

Required By Substantial Completion QC Checks

Spare.Name Definition The name of the item.

Example Value “AF-1” Required By Substantial Completion QC Checks 1. Must have a text value that is not n/a or empty

Spare.CreatedBy Definition The contact email of the person or company creating or updating a row of COBie data.

Example Value “Frank.Wright@InspiredArch.com” Required By Substantial Completion QC Checks 1. Must have a text value that is not n/a or empty

2. Must match a referenced Name column in another Contact.Email

Spare.CreatedOn Definition The date on which the information provided in a row of COBie data was created or updated by the person or company identified in the creat-ed by field.

Example Value “2019-01-25 16:00:03” Required By Substantial Completion QC Checks 1. Must have a text value that is not n/a or empty

2. Must be a valid date, in ISO format (YYYY-MM-DD HH:MM:SS)

Spare.Name Definition The name of the item.

Example Value “AF-1” Required By Substantial Completion QC Checks 1. Must have a text value that is not n/a or empty

Spare

Spare.Category Definition A classification of the type of information contained within one row.

The default values are: “Part”, “PartSet”, “Lubricant”, “Other”, “Spare”, and “SpareSet”.

Required By Substantial Completion QC Checks 1. Must have a text value that is not n/a or empty

Spare.TypeName Definition A foreign key…