Deliverables
There are four COBie deliverables identified in the COBie Guide. Two are required during design and two during construction. Design deliverables at the 35% and Construction Documents stage of design are required. Construction Deliverables at the Beneficial Occupancy and Fiscal Completion stage are required.
General Information
- Responsible
- Architect
- Expectations
- Deliverable should provide accurate representation of spaces and architectural assets, and outline expectations for building systems and services.
- Assets
- A single COBie Worksheet per building (facility) & Associated Revit Model(s)
Description
The Design and Development Deliverable is the first of the four standard COBie deliverables, and is intended to provide an accurate representation of space and architectural facility assets. At this stage, space assets only need to match the level of detail found in the associated drawings. Other assets such as doors, windows, plumbing, and lighting elements are only required by this deliverable if they are included in the accompanying drawings.
Recognizing systems for heating, cooling, electricity, water, fire protection, and other pertinent services are not likely to be designed at this stage, the Design and Development Deliverable only needs to identify the EXPECTATIONS of those systems. These systems only need to be identified by name and classification, and will not include any reference to the components comprising them.
The following table outlines the data expected to accompany this deliverable:
COBie Worksheet |
Required Content |
Contact |
One row for the designer’s BIM manager shall be provided. |
Facility |
One facility per COBie file. |
Floor |
One row for each vertical level to include foundations, floors, roofs, and site. |
Space |
One row per functional space, per room. Mult. spaces in a room possible. |
Zone |
One row for each COBie.Space and COBie.Zone type. |
Type |
One row for each scheduled product type found on design drawings. |
Component |
One row for each individual scheduled product found on design drawings. |
System |
One row for each system to be defined in the next stage of design. |
Document |
One row for each associated deliverable document linked to relevant sheet. |
One row listing URL of target product COBie.Type selected. |
Attribute |
One row for each required COBie.Space Attribute. |
One row for each required COBie.Type Attribute. |
One row for each required COBie.Component Attribute. |
General Information
- Responsible
- Architect coordinates all design disciplines.
- Expectations
- Complete design with all COBie data captured in a single Worksheet along with contributing Revit models.
- Assets
- A single COBie Worksheet per building (facility) & Associated Revit Model(s)
Description
The Construction Documents Design Deliverable should reflect the complete set of all spaces, scheduled products, and equipment presented in the accompanying drawings for all disciplines. Although numerous consultants may contribute to the deliverable, it is the Architects responsibly to coordinate the input from each discipline, and compile that information into a single COBie file.
Building upon the information included in the Design Development Deliverable, this deliverable is expected to represent a completed design including all spaces, scheduled products, and equipment assets presented in the drawings. Additionally, all products and equipment should be grouped into systems based on the services they provide throughout the building.
The following table outlines the data expected to accompany this deliverable:
COBie Worksheet |
Required Content |
Contact |
One row for the designer’s BIM manager shall be provided. |
Facility |
One facility per COBie file. |
Floor |
One row for each vertical level to include foundations, floors, roofs, and site. |
Space |
One row per functional space, per room. Mult. spaces in a room possible |
Zone |
One row for each COBie.Space and COBie.Zone type. |
Type |
One row for each scheduled product type found on design drawings |
Component |
One row for each individual scheduled product found on design drawings. |
System |
One row for each COBie.Component identifying the related COBie.System . |
Document |
"One row for each associated deliverable document. Linked to relevant sheet.
One row listing URL of target product COBie.Type selected." |
Attribute |
One row for each required COBie.Space Attribute.
One row for each required COBie.Type Attribute.
One row for each required COBie.Component Attribute |
General Information
- Responsible
- General Contractor
- Expectations
- Deliverable should reflect the as-installed and commissioned facility at the time of beneficial occupancy.
- Assets
- A single COBie Worksheet per building (facility) & Updated Revit Model(s) associated with project.
Description
Although the Commissioning Agent may assist the General Contractor for projects with third-party commissioning, the General Contractor is responsible for the Beneficial Occupancy Construction Deliverable. The COBie file and associated Revit models included with this deliverable should be an update to the assets submitted for the Construction Document Deliverable. Similar to other deliverables, only one COBie Worksheet should be submitted for each facility.
The following table outlines the data expected to accompany this deliverable:
COBie Worksheet |
Required Content |
Contact |
One row for the designer’s BIM manager shall be provided. |
Facility |
One facility per COBie file. |
Floor |
One row for each vertical level to include foundations, floors, roofs, and site. |
Space |
One space per functional use. |
Zone |
One row for each COBie.Space and COBie.Zone type. |
Type |
One row for each scheduled product type found on design drawings. |
Component |
One row for each individual scheduled product found on design drawings. |
System |
One row for each COBie.Component identifying the related COBie.System . |
Spare |
Row(s) for each spare, part, or lubricant for each COBie.Type |
Resource |
One row for each material, labor, training, or other required resource. |
Job |
Row(s) for each COBie.Type identifying PM Schedules
Row(s) for COBie.Types identifying Operations Schedules
Row(s) for COBie.Components identifying Operations Schedules |
Document |
Row(s) for each COBie.Type listing each approved submittal document.
Row(s) for each COBie.Type listing all commissioning submittals.
Row(s) for each COBie.Component listing all commissioning submittals.
One row for a photograph of each COBie.Component equipment nameplate. |
Attribute |
One row for each required COBie.Space Attribute.
One row for each required COBie.Type Attribute.
One row for each COBie.Component equipment nameplate information |
General Information
- Responsible
- General Contractor
- Expectations
- Deliverable should reflect the as-built documents delivered as fiscal completion of the project.
- Assets
- A single COBie Worksheet per building (facility) & Updated Revit Model(s) associated with project.
Description
Although the Commissioning Agent may assist the General Contractor for projects with third-party commissioning, the General Contractor is responsible for the As-Built Deliverable. The COBie file and associated Revit models included with this deliverable is expected to reflect information represented in the as-built documents delivered at a projects fiscal completion.
The following table outlines the data expected to accompany this deliverable:
COBie Worksheet |
Required Content |
Contact |
One row for the designer’s BIM manager shall be provided. |
Facility |
One facility per COBie file. |
Floor |
One row for each vertical level to include foundations, floors, roofs, and site. |
Space |
One space per functional use. |
Zone |
One row for each COBie.Space and COBie.Zone type. |
Type |
One row for each scheduled product type found on design drawings. |
Component |
One row for each individual scheduled product found on design drawings. |
System |
One row for each COBie.Component identifying the related COBie.System . |
Spare |
Row(s) for each spare, part, or lubricant for each COBie.Type |
Resource |
One row for each material, labor, training, or other required resource. |
Job |
Row(s) for each COBie.Type identifying PM Schedules
Row(s) for COBie.Types identifying Operations Schedules
Row(s) for COBie.Components identifying Operations Schedules |
Document |
Row(s) for each COBie.Type listing each approved submittal document.
Row(s) for each COBie.Type listing all commissioning submittals.
Row(s) for each COBie.Component listing all commissioning submittals.
One row for a photograph of each COBie.Component equipment nameplate. |
Attribute |
One row for each required COBie.Space Attribute.
One row for each required COBie.Type Attribute.
One row for each COBie.Component equipment nameplate information |
Quality Criteria
COBie design deliverables must reflect data about scheduled assets identified in the associated design deliverables. Since scheduled assets appear on drawings in design schedules, the COBie guide identifies the minimum requirement for schedule table headers. COBie construction deliverables must reflect updates to the designed assets and include construction and commissioning information consistent with that already produced in paper-based formats. Some key considerations include:
One Facility Per Deliverable
- A single COBie file should be created for each invividual building.
- Projects with multiple buildings should have a separate COBie file for each building.
- Sitework should be provided as a separate COBie file, even if a project only consists of a single building.
Unique Asset Naming
- All COBie related information should have unique names.
- Spaces are defined as functional areas; sequential letter designations should be used in cases where a physical room has several functional areas.
- Both Revit Spaces (MEP) and Rooms (Architecture) are used to define COBie spaces, and should be unique. See "Using COBie with Revit" for more information about this.
Categories
Large public clients manage different types of facilities on multiple campuses. In COBie this is accomplished through the use of several different types of Classifications. Classifications are “category codes” of different types used in COBie. Classifications are "category codes" of different types used in COBie. The NBIMS-US requires classification for the following COBie worksheets:
- Contact
- Facility
- Space
- Type
- System
NBIMS-US designates OmniClass as the default classification method used if no other method is specified in contract.
Zones
Buildings contain groups of spaces that, when connected, provide specific capabilities to the owner. The COBie.Zone
worksheet is designed to identify the spaces that make up a given zone.
In general, zones shall be identified by zone type and characteristics. Zones naming in large facilities shall also be identified floor and wing appended.
A COBie.Space
may only be listed once for a given type of zone. A COBie.Space
may, however, be part of multiple types of zones.
As an example consider Space “100” in a building where “Circulation Zone” and “Fire Protection” zoning information is required by the owner. In this example Space 100 could be part of the “Circulation Zone - Public” Circulation Zone and the “Fire Protection Zone - First Floor West Wing” Fire Protection Zone. It is not, however, possible for Space 100 to be part of both the “Fire Protection Zone - First Floor West Wing” and “Fire Protection Zone - First Floor East Wing" zones.
Zones may be nested. Nesting must be accomplished through the name of the zone. For example, there may be shared spaces that support both the “Fire Protection Zone - First Floor West Wing” and “Fire Protection Zone - First Floor East Wing” zone. Such zones can be identified in the “Fire Protection Zone - First Floor” zone.
System
Buildings contain groups of components that, when connected, provide specific required services. The COBie.System worksheet is designed to identify the components that make up a given system. In general, systems shall be identified by building service, floor and wing. Subsystems, if required, shall be identified using an owner-approved naming convention.
A COBie.Component
may only be listed once for a given type of system. A COBie.Component
may, however, be part of multiple types of systems.
As an example consider Component “Sensor – Temperature 101” in a building where “HVAC system” and “Sensor System” information is required by the owner. In this example, the sensor could be part of both the “HVAC System – Chilled Water” and the “BAS System – HVAC Sensors” system. It is not, however, possible for the sensor to be part of both the “HVAC System – Chilled Water” and “HVAC System – First Floor Heating Distribution” system.
Systems may be nested. Nesting must be accomplished through the name of the system. For example a Fire Protection System may have a set of equipment supporting “Fire Protection – Common” and equipment supporting specific areas of the building such a “Fire Protection – First Floor, West Wing” and a “Fire Protection - First Floor, East Wing”.
Units of Measure
COBie models require a single standard set of units of measure for linear, area, and volumetric measures. This unit of measure standard is applied on all units that do not otherwise have units attached. Designers shall designate the required units of measure for their projects for owner approval prior to starting design. All other disciplines shall be required to use the same units of measure defined by the designer.
The architectural model and all other models shall be oriented to “project” north. The difference between project north and magnetic north shall be defined by the architect. The designer shall designate the elevation of the project for a single origin point. Latitude and Longitude shall be defined based on the single origin point. All other disciplines shall be required to reference the project north rotation and elevation origin point designated by the designer.
Given the differences in software implementation of units, it is critical that the design team evaluate their product using small testing models to ensure that this requirement can be met. It would be expected that commercial product COBie points of contact will need to be identified and contacted to reduce post-design or post-construction manual updating of COBie deliverables.
During design the Architect shall be responsible for the manual update of all COBie.Attributes
not automatically provided by design software. During construction the Contractor or Commissioning Agent shall be responsible for the manual update of all COBie.Attributes
not automatically provided by software used to create their required deliverables.
Worksheets
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
People/offices/companies referenced in a file. |
Primary Author |
Anyone that provides or creates COBie data. |
Secondary Author |
N/A |
Notes |
At least one contact must be provided. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Email |
Unique e-mail address of the contact |
tjm@caddmicro.com |
B |
CreatedBy |
E-mail address of the contact who created the current contact |
tjm@caddmicro.com |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Role |
E |
Company |
Company name |
CADD Microsystems, Inc. |
F |
Phone |
Phone number |
+1 (703) 719-0500 |
G |
ExternalSystem |
Software used (Revit Build Information) |
Autodesk Revit 2013, Build: 20121003_2115(x64) |
H |
ExternalObject |
Revit API class and category |
Autodesk.Revit.DB.FamilyInstance:OST_Doors |
I |
ExternalIdentifier |
Revit Element ID or GUID (Global Unique IDentifier) |
169233 |
J |
Department |
Department name |
Professional Solutions Group |
K |
OrganizationCode |
Organization code |
CADD |
L |
GivenName |
First name |
T.J. |
M |
FamilyName |
Last name |
Meehan |
N |
Street |
Street address |
6361 Walker Lane, Suite 400 |
O |
PostalBox |
Post Office (P.O.) Box |
PO Box 4292 |
P |
Town |
City / town |
Alexandria |
Q |
StateRegion |
State or region |
Virginia |
R |
PostalCode |
Zip / postal code |
22310 |
S |
Country |
Country |
USA |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Project, site, and facility information. |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
Typically there is only one facility (and, therefore, only one row) per COBie file. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique name of the facility |
6361 Walker Lane |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
Picklists.Category-Facility |
E |
ProjectName |
Name of the project |
Metro Park VI |
F |
SiteName |
Name of the site |
Metro Park Office Complex |
G |
LinearUnits |
PickLists.Units-Linear |
PickLists.Units-Linear |
H |
AreaUnits |
PickLists.Units-Area |
PickLists.Units-Area |
I |
VolumeUnits |
PickLists.Units-Volume |
PickLists.Units-Volume |
J |
CurrencyUnit |
PickLists.Units-Currency |
PickLists.Units-Currency |
K |
AreaMeasurement |
Area measurement standard used |
ANSI/BOMA Z65.1—2010 |
L |
ExternalSystem |
See reference |
Contact.ExternalSystem |
M |
ExternalProjectObject |
The IFC field used for the project (IfcProject) |
IfcProject |
N |
ExternalProjectIdentifier |
The GUID of the IfcProject field |
1TB8MXxlf6BAI7EOFPDWY8 |
O |
ExternalSiteObject |
The IFC field used for the site (IfcSite) |
IfcSite |
P |
ExternalSiteIdentifier |
The GUID of the IfcSite field |
1TB8MXxlf6BAI7EOFPDWYA |
Q |
ExternalFacilityObject |
The IFC field used for the facility (IfcBuilding) |
IfcBuilding |
R |
ExternalFacilityIdentifier |
The GUID of the IfcSite field |
1TB8MXxlf6BAI7EOFPDWY9 |
S |
Description |
Description of the facility |
Metro Park VI office building |
T |
ProjectDescription |
Description of the project |
11 story office building |
U |
SiteDescription |
Description of the site |
Metro Park Campus |
V |
Phase |
Defines the phase of this project |
Phase 1 |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Description of vertical levels (floors, roofs, foundations, exterior areas, etc.). |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
One row for each vertical level to include foundations, floors, roofs, and site. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique floor number / designator |
Level 1 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
Picklists.Category-Floor |
E |
ExternalSystem |
See reference |
Contact.ExternalSystem |
F |
ExternalObject |
See reference |
PickLists.objFloor |
G |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
H |
Description |
Description of the floor |
First floor, ground level |
I |
Elevation |
Elevation of the floor as a numeric value using the 'LinearUnits' value from the 'Facility' worksheet as the units of measurement |
14.1 |
J |
Height |
Height of the floor as a numeric value using the 'LinearUnits' value from the 'Facility' worksheet as the units of measurement |
13.0 |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Spaces/rooms identified within a given floor. |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
One row per functional space/room. Multiple spaces in a room possible. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique room number / designator |
101 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Space |
E |
FloorName |
See reference |
Floor.Name |
F |
Description |
Room name / description |
Office |
G |
ExternalSystem |
See reference |
Contact.ExternalSystem |
H |
ExternalObject |
See reference |
PickLists.objSpace |
I |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
J |
RoomTag |
The name of the room that is used on the signage after construction |
Electrical |
K |
UsableHeight |
Usable height of the space as a numeric value using the 'LinearUnits' value from the 'Facility' worksheet as the units of measurement |
8.5 |
L |
GrossArea |
Gross area of the space as a numeric value using the 'AreaMeasurement' as the standard and the 'AreaUnits' value as the units of measurement from the 'Facility' worksheet |
107.3 |
M |
NetArea |
Net area of the space as a numeric value using the 'AreaMeasurement' as the standard and the 'AreaUnits' value as the units of measurement from the 'Facility' worksheet |
92.6 |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Sets of spaces shring a specific attribute. |
Primary Author |
Designer |
Secondary Author |
|
Notes |
One row for each COBie.Space and COBie.Zone type. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique zone number / designator |
1 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
Picklists.Category-Zone |
E |
SpaceNames |
See reference |
Space.Name |
F |
ExternalSystem |
See reference |
Contact.ExternalSystem |
G |
ExternalObject |
See reference |
PickLists.objZone |
H |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
I |
Description |
Zone name / description |
1st Floor, East wing |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Types of equipment, products, and materials. |
Primary Author |
Designer |
Secondary Author |
|
Notes |
One row for each scheduled product type found in the design drawings. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique name for each type of item |
Horizontal Low Profile FCU |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Product |
E |
Description |
Description of the item |
Horizontal Low Profile Fan-Coil Units (FCU) |
F |
AssetType |
See reference |
PickLists.Type-AssetType |
G |
Manufacturer |
Email of the manufacturer |
xxx@johnsoncontrols.com |
H |
ModelNumber |
Manufacturer's model number |
T602 |
I |
WarrantyGuarantorParts |
Email of company responsible for warrantying the parts |
xxx@johnsoncontrols.com |
J |
WarrantyDurationParts |
Length of the warranty with regard to parts for this item |
3 |
K |
WarrantyGuarantorLabor |
Email of company responsible for warrantying the labor |
xxx@johnsoncontrols.com |
L |
WarrantyDurationLabor |
Length of the warranty with regard to labor for this item |
3 |
M |
WarrantyDurationUnit |
See reference |
PickLists.Units-Duration |
N |
ExternalSystem |
See reference |
Contact.ExternalSystem |
O |
ExternalObject |
See reference |
PickLists.objType |
P |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
Q |
ReplacementCost |
Cost to replace |
725 |
R |
ExpectedLife |
|
S |
DurationUnit |
See reference |
PickLists.Units-Duration |
T |
WarrantyDescription |
|
U |
NominalLength |
|
V |
NominalWidth |
|
W |
NominalHeight |
|
X |
ModelReference |
|
Y |
Shape |
|
|
Z |
Size |
|
|
AA |
Color |
|
|
AB |
Finish |
|
|
AC |
Grade |
|
|
AD |
Material |
|
|
AE |
Constituents |
|
AF |
Features |
|
|
AG |
AccessibilityPerformance |
|
AH |
CodePerformance |
|
AI |
SustainabilityPerformance |
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Individually named materials and equipment. |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
One row for each individual scheduled product found in the design drawings. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique identifier of the component |
AHU-1 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
TypeName |
See reference |
Type.Name |
E |
Space |
See reference |
Space.Name |
F |
Description |
Description of the component |
Air Handling Unit 1 |
G |
ExternalSystem |
See reference |
Contact.ExternalSystem |
H |
ExternalObject |
See reference |
PickLists.objComponent |
I |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
J |
SerialNumber |
Component serial number |
3 Z F 12345 00 |
K |
InstallationDate |
Date of installation |
1900-12-31 |
L |
WarrantyStartDate |
Date of the start of the warranty period |
1900-12-31 |
M |
TagNumber |
|
|
N |
BarCode |
|
|
O |
AssetIdentifier |
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Components that go together to perform a certain function. |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
One row for each system to be defined in the next stage of design. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique name for each system |
Mechanical Supply Air 1 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
Picklists.Category-Element |
E |
ComponentNames |
List of all components that are part of the system |
AHU-1, VAV-1, VAV-2, CF-1, CF-2, CF-3 |
F |
ExternalSystem |
See reference |
Contact.ExternalSystem |
G |
ExternalObject |
See reference |
PickLists.objSystem |
H |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
I |
Description |
Description of the system |
Mechanical supply air system serving first floor lobby |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Components having constituent components. |
Primary Author |
Designer |
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
Unique name for each assembly |
Air Handling Unit 1 |
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
SheetName |
See reference |
PickLists.SheetName-Assembly |
E |
ParentName |
See reference |
Component.Name |
F |
ChildNames |
See reference |
Component.Name |
G |
AssemblyType |
See reference |
PickLists.Assembly-AssemblyType |
H |
ExternalSystem |
See reference |
Contact.ExternalSystem |
I |
ExternalObject |
See reference |
PickLists.objAssembly |
J |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
K |
Description |
Description of the assembly |
Components of Air Handling Unit 1 |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Logical connections between components. |
Primary Author |
Designer |
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
ConnectionType |
See reference |
PickLists.Category-Connection |
E |
SheetName |
See reference |
PickLists.SheetName |
F |
RowName1 |
See reference |
Component.Name |
G |
RowName2 |
See reference |
Component.Name |
H |
RealizingElement |
See reference |
Component.Name |
I |
PortName1 |
See reference |
- |
J |
PortName2 |
See reference |
- |
K |
ExternalSystem |
See reference |
Contact.ExternalSystem |
L |
ExternalObject |
See reference |
PickLists.objConnection |
M |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
N |
Description |
|
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
UK Only |
|
|
|
|
Worksheet Summary
Content |
Economic, environmental, and social impacts at various stages in the life cycle. |
Primary Author |
|
Secondary Author |
|
Notes |
Optionally with a flexible repeating pattern. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
ImpactType |
See reference |
PickLists.Category-Impact |
E |
ImpactStage |
See reference |
PickLists.Impact-ImpactStage |
F |
SheetName |
See reference |
PickLists.SheetName |
G |
RowName |
See reference |
- |
H |
Value |
|
|
I |
ImpactUnit |
See reference |
PickLists.Units-Impact |
J |
LeadInTime |
|
|
K |
Duration |
|
|
L |
LeadOutTime |
|
M |
ExternalSystem |
See reference |
Contact.ExternalSystem |
N |
ExternalObject |
See reference |
PickLists.objImpact |
O |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
P |
Description |
|
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Onsite and replacement parts and reordering information. |
Primary Author |
Construction Contractor |
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Spare |
E |
TypeName |
See reference |
Type.Name |
F |
Suppliers |
See reference |
Contact.Email |
G |
ExternalSystem |
See reference |
Contact.ExternalSystem |
H |
ExternalObject |
See reference |
PickLists.objSpare |
I |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
J |
Description |
|
|
K |
SetNumber |
|
|
L |
PartNumber |
|
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Required materials, tools, and training. |
Primary Author |
Construction Contractor |
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Resource |
E |
ExternalSystem |
See reference |
Contact.ExternalSystem |
F |
ExternalObject |
See reference |
PickLists.objResource |
G |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
H |
Description |
|
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Procedures needed to maintain and operate the facility. |
Primary Author |
|
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Job |
E |
Status |
See reference |
PickLists.Job-Status |
F |
TypeName |
See reference |
Type.Name |
G |
Description |
|
|
H |
Duration |
|
|
I |
DurationUnit |
See reference |
PickLists.Units-Duration |
J |
Start |
|
|
K |
TaskStartUnit |
See reference |
PickLists.Units-Duration |
L |
Frequency |
|
|
M |
FrequencyUnit |
See reference |
PickLists.Units-Duration |
N |
ExternalSystem |
See reference |
Contact.ExternalSystem |
O |
ExternalObject |
See reference |
PickLists.objJob |
P |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
Q |
TaskNumber |
|
R |
Priors |
See reference |
Job.TaskNumber |
S |
ResourceNames |
See reference |
Resource.Name |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
All applicable document references. |
Primary Author |
Construction Contractor |
Secondary Author |
Manufacturers, Subcontractor(s) |
Notes |
All documents referenced shall be submitted with the COBie data. Default format for documents, unless otherwise notified, should be Portable Document Format (PDF). Documents identified here are referenced through the remainder of the COBie format, where appropriate. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Document |
E |
ApprovalBy |
See reference |
PickLists.Document-ApprovalBy |
F |
Stage |
See reference |
PickLists.Stage |
G |
SheetName |
See reference |
PickLists.SheetName |
H |
RowName |
See reference |
- |
I |
Directory |
|
|
J |
File |
|
|
K |
ExternalSystem |
See reference |
Contact.ExternalSystem |
L |
ExternalObject |
See reference |
PickLists.objDocument |
M |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
N |
Description |
|
|
O |
Reference |
|
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Designer |
Primary Author |
Anyone that provides or creates COBie data. |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
If specific attributes are defined by the enabling contract documents, these attributes shall be provided in this worksheet. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Stage |
E |
SheetName |
See reference |
PickLists.SheetName |
F |
RowName |
See reference |
- |
G |
Value |
|
|
H |
Unit |
|
|
I |
ExternalSystem |
See reference |
Contact.ExternalSystem |
J |
ExternalObject |
See reference |
PickLists.objAttribute |
K |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
L |
Description |
|
|
M |
AllowedValues |
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Location of spaces and components: boxes (3D), lines (2D), and points (1D). |
Primary Author |
Designer |
Secondary Author |
Construction Contractor (updates with as-built data) |
Notes |
If coordinates for specific parts of the facility are required by the enabling contract documents, those coordinates shall be provided in this worksheet. |
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Category |
See reference |
PickLists.Category-Coordinate |
E |
SheetName |
See reference |
PickLists.SheetName-Coordinate |
F |
RowName |
See reference |
- |
G |
CoordinateXAxis |
|
H |
CoordinateYAxis |
|
I |
CoordinateZAxis |
|
J |
ExternalSystem |
See reference |
Contact.ExternalSystem |
K |
ExternalObject |
See reference |
PickLists.objCoordinate |
L |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
M |
ClockwiseRotation |
|
N |
ElevationalRotation |
|
O |
YawRotation |
|
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Other required handover issues. |
Primary Author |
|
Secondary Author |
|
Notes |
|
Worksheet Details
Col |
Name |
Description |
Example |
A |
Name |
|
|
B |
CreatedBy |
See reference |
Contact.Email |
C |
CreatedOn |
Date and time created |
1900-12-31T23:59:59 |
D |
Type |
See reference |
PickLists.Category-Issue |
E |
Risk |
See reference |
PickLists.Issue-Risk |
F |
Chance |
See reference |
PickLists.Issue-Chance |
G |
Impact |
See reference |
PickLists.Issue-Impact |
H |
SheetName1 |
See reference |
PickLists.SheetName |
I |
RowName1 |
See reference |
|
J |
SheetName2 |
See reference |
PickLists.SheetName |
K |
RowName2 |
See reference |
|
L |
Description |
|
|
M |
Owner |
See reference |
Contact.Email |
N |
Mitigation |
|
|
O |
ExternalSystem |
See reference |
Contact.ExternalSystem |
P |
ExternalObject |
See reference |
PickLists.objIssue |
Q |
ExternalIdentifier |
See reference |
Contact.ExternalIdentifier |
Required |
Revit |
Program |
Design |
Build |
Operate |
|
|
|
|
|
|
Worksheet Summary
Content |
Lists of available values for reference fields. |
Primary Author |
Anyone that provides or creates COBie data. |
Secondary Author |
|
Notes |
|
Worksheet Details
Sample Content