U.S. General Services Administration
BIM Technical Standards: Minimum Attributes
At an absolute minimum, the following non-visual data must be attached to model data. The creator of the data is only responsible for attaching these fields to the object. The party responsible for entering the data will vary and should be defined within the project BEP. Completion of this information corresponds with Level of Detail (LOD) requirements defined by GSA requirements.
The minimum attributes are further defined in the Level of Detail section of the site. They are to be followed and may not be overridden in the BEP. What level an individual firm is responsible for will vary and is defined in either the standard Model Progression Matrix or a custom MPM that was defined as part of the project's BEP.
- Detailed Object Definitions
- Model Progression Matrix
Standard
General:
- When authoring data within Autodesk Revit, the GSA provided Shared Parameters file must be used, with no exceptions.
- When possible, data created outside of the Revit platform must be defined using the same GUID found in the Revit Shared Parameters file to identify the property.
- If an attribute is provided, it will be used and not duplicated under a different name.
COBie Data
In the following table, the minimum COBie attributes for your BIM are defined. This list is intended to be the very minimum for your BIM to be accepted by GSA. Actual deployment of COBie on your project must be defined within the project BEP. For additional guidance on deploying COBie on your project, see the COBie Tutorial section of the site.
Responsibility for COBie data will almost always be shared between the designers and builders on a project. The responsible party listed below is the default breakdown for GSA work. It is expected that each team will review and adjust this list as part of the BEP development.
| Attribute / Parameter | Data Type | Description | Responsible Party |
|---|---|---|---|
| COBie-Floor-CreatedBy | TEXT | The email address of the user who created the object. | Design team |
| COBie-Floor-Elevation | TEXT | Height above datum. | Design team |
| COBie-Floor-ExtSystem | TEXT | Information on the creating application. | Design team |
| COBie-Floor-CreatedOn | TEXT | Date the object was created. | Design team |
| COBie-Floor-Height | NUMBER | Floor to floor height. | Design team |
| COBie-Floor-Description | TEXT | Extended description of the object. | Design team |
| COBie-Floor-ExtIdentifier | TEXT | Information on the creating application. | Design team |
| COBie-Floor-Category | TEXT | Category of the floor (Site, Floor, Roof). | Design team |
| COBie-Floor-ExtObject | TEXT | Information on the creating application. | Design team |
| COBie-Floor-Name | TEXT | Unique name of the floor. | Design team |
| COBie-Space-ExtSystem | TEXT | Information on the creating application. | Design team |
| COBie-Space-Category | TEXT | Category of space. What kind of space is it? (OmniClass Table 13 Space Function) | Design team |
| COBie-Space-ExtObject | TEXT | Information on the creating application. | Design team |
| COBie-Space-UsableHeight | NUMBER | Used for COBie based data exchange. | Design team |
| COBie-Space-ExtIdentifier | TEXT | Information on the creating application. | Design team |
| COBie-Space-CreatedOn | TEXT | Date the object was created. | Design team |
| COBie-Space-FloorName | TEXT | Lowest floor in which space appears | Design team |
| COBie-Space-Description | TEXT | Extended description of the object. | Design team |
| COBie-Space-GrossArea | NUMBER | Used for COBie based data exchange. | Design team |
| COBie-Space-NetArea | NUMBER | Used for COBie based data exchange. | Design team |
| COBie-Space-Name | TEXT | Unique space name primary key for all spaces. | Design team |
| COBie-Space-CreatedBy | TEXT | The email address of the user who created the object. | Design team |
| COBie-Space-RoomTag | TEXT | Room tag provides door number for building occupant | Design team |
| COBie-Zone-CreatedBy | TEXT | The email address of the user who created the object. | Design team |
| COBie-Zone-SpaceNames | TEXT | Used for COBie based data exchange. | Design team |
| COBie-Zone-ExtObject | TEXT | Information on the creating application. | Design team |
| COBie-Zone-Description | TEXT | Extended description of the object. | Design team |
| COBie-Zone-ExtIdentifier | TEXT | Information on the creating application. | Design team |
| COBie-Zone-Category | TEXT | Used for COBie based data exchange. | Design team |
| COBie-Zone-Name | TEXT | Used for COBie based data exchange. | Design team |
| COBie-Zone-CreatedOn | TEXT | Date the object was created. | Design team |
| COBie-Zone-ExtSystem | TEXT | Information on the creating application. | Design team |
| COBie-Type-WarrantyDurationUnit | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-ModelNumber | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-AssetType | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-WarrantyDescription | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-WarrantyDurationLabor | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-Description | TEXT | Extended description of the object. | Construction team |
| COBie-Type-ReplacementCost | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-CreatedBy | TEXT | The email address of the user who created the object. | Construction team |
| COBie-Type-ExtObject | TEXT | Information on the creating application. | Construction team |
| COBie-Type-ExpectedLife | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-WarrantyDurationParts | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-WarrantyGuarantorParts | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-Category | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-WarrantyGuarantorLabor | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-DurationUnit | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-Name | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-CreatedOn | TEXT | Date the object was created. | Construction team |
| COBie-Type-Manufacturer | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Type-ExtSystem | TEXT | Information on the creating application. | Construction team |
| COBie-Type-ExtIdentifier | TEXT | Information on the creating application. | Construction team |
| COBie-Component-SerialNumber | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-Name | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-TagNumber | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-WarrantyStartDate | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-ExtIdentifier | TEXT | Information on the creating application. | Construction team |
| COBie-Component-ExtSystem | TEXT | Information on the creating application. | Construction team |
| COBie-Component-TypeName | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-CreatedBy | TEXT | The email address of the user who created the object. | Construction team |
| COBie-Component-BarCode | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-InstallationDate | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-Description | TEXT | Extended description of the object. | Construction team |
| COBie-Component-CreatedOn | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-AssetIdentifier | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-Component-ExtObject | TEXT | Information on the creating application. | Construction team |
| COBie-Component-Space | TEXT | Used for COBie based data exchange. | Construction team |
| COBie-System-ExtObject | TEXT | Information on the creating application. | Design team |
| COBie-System-CreatedOn | TEXT | Date the object was created. | Design team |
| COBie--Description | TEXT | Extended description of the object. | N/A |
| COBie-System-CreatedBy | TEXT | The email address of the user who created the object. | Design team |
| COBie-System-ExtIdentifier | TEXT | Information on the creating application. | Design team |
| COBie-System-ComponentNames | TEXT | Used for COBie based data exchange. | Design team |
| COBie-System-ExtSystem | TEXT | Information on the creating application. | Design team |
| COBie-System-Category | TEXT | Used for COBie based data exchange. | Design team |
| COBie-System-Name | TEXT | Used for COBie based data exchange. | Design team |
| COBie-Attribute-SheetName | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-CreatedBy | TEXT | The email address of the user who created the object. | Shared |
| COBie-Attribute-CreatedOn | TEXT | Date the object was created. | Shared |
| COBie-Attribute-ExtSystem | TEXT | Information on the creating application. | Shared |
| COBie-Attribute-Name | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-RowName | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-ExtIdentifier | TEXT | Information on the creating application. | Shared |
| COBie-Attribute-Unit | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-Category | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-ExtObject | TEXT | Information on the creating application. | Shared |
| COBie-Attribute-Value | TEXT | Used for COBie based data exchange. | Shared |
| COBie-Attribute-Description | TEXT | Extended description of the object. | Shared |
URL Data
URL data is to be added to all projects as a TYPE level parameter or attribute. The URL data will link to either a specific file or a folder based on whether the target data is a single file, such as an MSDS sheet, or multiple files, such as photos. The targeted data is to follow the structure outlined in the Data Submittal Standard.
All links must be relative and follow the URL guidelines outlined in the Referencing and Linking section of the standard. Links containing "hard" paths will be rejected.
| Attribute / Parameter | Data Type | Description |
|---|---|---|
| URL As-Built Drawings | URL | A URL link pointing to one or more as-built drawings, typically either DWGs or PDFs |
| URL MSDS | URL | A URL link pointing to one or more MSDS, typically a single PDF |
| URL Op and Maint Manuals | URL | A URL link pointing to one or more operation or maintenance manuals, typically PDFs |
| URL Owner Manual | URL | A URL link pointing to one or more owner manuals, typically PDFs |
| URL Photos | URL | A URL link pointing to one or more digital photographs, typically JPGs. This may link to a sub-folder of the divisions Photos folder when required. |
| URL Product Data | URL | A URL link pointing to one or more product data or information documents, typically PDFs |
| URL RFIs | URL | A URL link pointing to one or more scanned RFIs from the project, typically PDFs, although sometimes JPGs |
| URL Shop Drawings | URL | A URL link pointing to one or more shop drawings, typically DWGs or PDFs |
| URL Sketches | URL | A URL link pointing to one or more sketches, typically DWGs, PDFs, or JPGs |
| URL Warranty Information | URL | A URL link pointing to one or more documents containing warranty information, typically PDFs |
URL Guidelines
Most BIM applications allow for the attaching of URLs (Universal Resource Locators) to individual BIM objects. This allows for many forms of data to be connected directly to the BIM object.
When using URLs in as-built or record data for GSA, there are certain rules that need to be followed to ensure that the URLs will continue to work once the data is submitted.
Standard
General:
- All URLs must be verified as working prior to the submittal of the data to GSA.
URL to Local Files:
- All URLs used in submitted data must be of the relative and never pathed to a absolute network location.
- Valid use: .\Concrete\Warranty Info\Warranty.pdf
- Invalid use: E:\Models\Concrete\Warranty Info\Warranty.pdf
- URLs should always go deeper into the folder structure. Backlinking should be avoided whenever possible.
- Valid use: .\Concrete\Warranty Info\Warranty.pdf
- Invalid use: ..\..\Concrete\Warrant Info\Warranty.pdf
URL to Internet Address:
- Care must be used when linking to internet based resources. It is unlikely that they will be available, with address unchanged, for the life-cycle of the building.
- Internet URLs must only be used when there is no means of making the content local to the data submittal.
Spatial Data (SDM)
| Attribute / Parameter | Data Type | Description |
|---|---|---|
| AB Name | Text | - |
| AB Short Name | Text | - |
| ANSI.BOMA Category Description | Text | - |
| Architectural Room Number | Text | - |
| Building Number | Text | - |
| Building Specific Room Name | Text | - |
| CBR Number | Text | - |
| Ceiling Height | Length | - |
| Occupant | Text | - |
| Occupant Organization Abbreviation | Text | - |
| Occupant Organization Code | Text | - |
| Occupant Organization Name | Text | - |
| Required Area | Text | - |
| Room Name | Text | - |
| Space Category Description | Text | - |
| Space Type Description | Text | - |
Green Building Properties
| Attribute / Parameter | Data Type | Description | Responsible Party |
|---|---|---|---|
| Recycled Content | Number | Percent of the item's content that is recycled. | Shared |
| Pre-Consumer Recycled Content | Number | Percent of the item's content that is pre-consumer recycled. | Shared |
| Post-Industrial Recycled Content | Number | Percent of the item's content that is post-industrial recycled. | Shared |
| Post-Consumer Recycled Content | Number | Percent of the item's content that is post-consumer recycled. | Shared |
| Manufacturer Location | Text | Location of item's manufacturer. | Shared |
| Item is New | Yes/No | Is the item new | Shared |
Omniclass Number
Design components used to generate the virtual model must be associated with an Omniclass Number and Omniclass Title. This allows for organization and understanding of design intent. This effort occurs in all design and construction phases. Within a Revit environment, it can be addressed in the family. The family templates generated by the GSA have this information already, however, if the predetermined information is not accurate to the component, it is the responsibility of either AE or GC (based on LOD) to be corrected.